# GHSA-4jmp-x7mh-rgmr: Finality Provider vulnerable to anti-slashing bypassing due to misconfiguration

> Attackers can bypass anti-slashing protections and cause slashing if EOTS manager endpoints are publicly accessible without HMAC protection.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 12 Dec 2025
- **Also known as:** GO-2025-4236

## What is GHSA-4jmp-x7mh-rgmr?

GHSA-4jmp-x7mh-rgmr is a vulnerability in github.com/babylonlabs-io/finality-provider, published on 12 Dec 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official 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

## Which versions are affected by GHSA-4jmp-x7mh-rgmr?

5 open source packages ship an affected version, including github.com/babylonlabs-io/finality-provider.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/babylonlabs-io/finality-provider` | Go | All versions | None |
| `github.com/babylonlabs-io/finality-provider` | Go | All versions | None |
| `github.com/babylonlabs-io/finality-provider` | Go | All versions | None |
| `github.com/babylonlabs-io/finality-provider` | Go | All versions | 1.0.4 |
| `github.com/babylonlabs-io/finality-provider` | Go | All versions | 1.0.4 |

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

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

## Is GHSA-4jmp-x7mh-rgmr being exploited?

There is no known exploitation of GHSA-4jmp-x7mh-rgmr in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-4jmp-x7mh-rgmr and fix it if it is affected.

What it is: GHSA-4jmp-x7mh-rgmr is a vulnerability in github.com/babylonlabs-io/finality-provider, published on 12 Dec 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of GHSA-4jmp-x7mh-rgmr in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/babylonlabs-io/finality-provider (Go): affected all versions; no fix listed
- github.com/babylonlabs-io/finality-provider (Go): affected all versions; no fix listed
- github.com/babylonlabs-io/finality-provider (Go): affected all versions; no fix listed
- github.com/babylonlabs-io/finality-provider (Go): affected all versions; fixed in 1.0.4
- github.com/babylonlabs-io/finality-provider (Go): affected all versions; fixed in 1.0.4

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/GHSA-4jmp-x7mh-rgmr/ (Markdown: https://insights.sbomify.com/GHSA-4jmp-x7mh-rgmr/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-4jmp-x7mh-rgmr

---
From sbomify Insights: https://insights.sbomify.com/GHSA-4jmp-x7mh-rgmr/
Summaries are generated and may contain mistakes; the official description above is the record.