How severe is GHSA-4jmp-x7mh-rgmr?

No CVSS score has been assigned to GHSA-4jmp-x7mh-rgmr yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-4jmp-x7mh-rgmr?

GHSA-4jmp-x7mh-rgmr affects the following packages: github.com/babylonlabs-io/finality-provider (Go), github.com/babylonlabs-io/finality-provider (Go), github.com/babylonlabs-io/finality-provider (Go), github.com/babylonlabs-io/finality-provider (Go). Ecosystems affected: Go.

How do I fix GHSA-4jmp-x7mh-rgmr?

Update github.com/babylonlabs-io/finality-provider to 1.0.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-4jmp-x7mh-rgmr is resolved across your whole dependency graph.

How do I detect GHSA-4jmp-x7mh-rgmr in my Go dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/babylonlabs-io/finality-provider. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-4jmp-x7mh-rgmr if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-4jmp-x7mh-rgmr?

O3 pinpoints whether GHSA-4jmp-x7mh-rgmr is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-4jmp-x7mh-rgmr actively exploited in the wild?

No public exploit code has been indexed for GHSA-4jmp-x7mh-rgmr yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

When was GHSA-4jmp-x7mh-rgmr published, and has it been updated?

GHSA-4jmp-x7mh-rgmr was published on December 12, 2025 and was last updated on February 3, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐹 Go

GHSA-4jmp-x7mh-rgmr

Finality Provider vulnerable to anti-slashing bypassing due to misconfiguration

Also known asGO-2025-4236

Published

Dec 12, 2025

Updated

Feb 3, 2026

Affected

4 pkgs

Patched

1 / 4

Exploits

None indexed

Blast Radius

4 pkgs affected

🐹github.com/babylonlabs-io/finality-provider🐹github.com/babylonlabs-io/finality-provider🐹github.com/babylonlabs-io/finality-provider🐹github.com/babylonlabs-io/finality-provider

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.

Description

Summary

The anti-slashing is not effective if the attacker can access EOTS manager endpoints.

Impact

If the EOTS manager endpoints are open to public without HMAC protection, the attacker can manually cause slashing of the finality provider through the RPC endpoints.

Report credits go to: x.com/RebelsRunways

Affected Packages

4 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/babylonlabs-io/finality-provider`	all versions	1.0.4
🐹Go	`github.com/babylonlabs-io/finality-provider`	all versions	No fix
🐹Go	`github.com/babylonlabs-io/finality-provider`	all versions	No fix
🐹Go	`github.com/babylonlabs-io/finality-provider`	all versions	No fix

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/babylonlabs-io/finality-provider. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update github.com/babylonlabs-io/finality-provider to 1.0.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-4jmp-x7mh-rgmr is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-4jmp-x7mh-rgmr is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-4jmp-x7mh-rgmr. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### Summary The anti-slashing is not effective if the attacker can access EOTS manager endpoints. ### Impact If the EOTS manager endpoints are open to public without HMAC protection, the attacker can manually cause slashing of the finality provider through the RPC endpoints. Report credits go to: x.com/RebelsRunways

O3 Security · Impact-Aware SCA

Is GHSA-4jmp-x7mh-rgmr in your dependencies?

O3 detects GHSA-4jmp-x7mh-rgmr across Go dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works