What is GHSA-4JMP-X7MH-RGMR?

GHSA-4JMP-X7MH-RGMR is a high-severity security vulnerability in github.com/babylonlabs-io/finality-provider (go), affecting versions <= 1.0.3. It is fixed in 1.0.4.

Which versions of github.com/babylonlabs-io/finality-provider are affected by GHSA-4JMP-X7MH-RGMR?

github.com/babylonlabs-io/finality-provider (go) versions <= 1.0.3 is affected.

Is there a fix for GHSA-4JMP-X7MH-RGMR?

Yes. GHSA-4JMP-X7MH-RGMR is fixed in 1.0.4. Upgrade to this version or later.

Is GHSA-4JMP-X7MH-RGMR exploitable, and should I be worried?

Whether GHSA-4JMP-X7MH-RGMR is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether GHSA-4JMP-X7MH-RGMR is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

GHSA-4JMP-X7MH-RGMR

Q: Which versions of github.com/babylonlabs-io/finality-provider are affected by GHSA-4JMP-X7MH-RGMR?

github.com/babylonlabs-io/finality-provider (go) versions <= 1.0.3 is affected.

Q: Is there a fix for GHSA-4JMP-X7MH-RGMR?

Yes. GHSA-4JMP-X7MH-RGMR is fixed in 1.0.4. Upgrade to this version or later.

Q: Is GHSA-4JMP-X7MH-RGMR exploitable, and should I be worried?

Whether GHSA-4JMP-X7MH-RGMR is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether GHSA-4JMP-X7MH-RGMR is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Q: How do I fix GHSA-4JMP-X7MH-RGMR?

Upgrade github.com/babylonlabs-io/finality-provider to 1.0.4 or later.

Summary

Finality Provider vulnerable to anti-slashing bypassing due to misconfiguration

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 versions

github.com/babylonlabs-io/finality-provider (<= 1.0.3) github.com/babylonlabs-io/finality-provider (= 1.1.0-rc.0) github.com/babylonlabs-io/finality-provider (= 1.1.0-rc.1) github.com/babylonlabs-io/finality-provider (= 1.99.0-devnet.6)

Security releases

github.com/babylonlabs-io/finality-provider → 1.0.4 (go)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

Upgrade github.com/babylonlabs-io/finality-provider to 1.0.4 or later to resolve this vulnerability.

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently Asked Questions

What is GHSA-4JMP-X7MH-RGMR? GHSA-4JMP-X7MH-RGMR is a high-severity security vulnerability in github.com/babylonlabs-io/finality-provider (go), affecting versions <= 1.0.3. It is fixed in 1.0.4.
Which versions of github.com/babylonlabs-io/finality-provider are affected by GHSA-4JMP-X7MH-RGMR? github.com/babylonlabs-io/finality-provider (go) versions <= 1.0.3 is affected.
Is there a fix for GHSA-4JMP-X7MH-RGMR? Yes. GHSA-4JMP-X7MH-RGMR is fixed in 1.0.4. Upgrade to this version or later.
Is GHSA-4JMP-X7MH-RGMR exploitable, and should I be worried? Whether GHSA-4JMP-X7MH-RGMR is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether GHSA-4JMP-X7MH-RGMR is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix GHSA-4JMP-X7MH-RGMR? Upgrade github.com/babylonlabs-io/finality-provider to 1.0.4 or later.