# CVE-2025-59942: go-f3 module vulnerable to integer overflow leading to panic

> An attacker can crash Filecoin nodes by sending specially crafted messages that trigger an integer overflow in the go-f3 library.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 29 Sep 2025
- **Updated:** 30 Sep 2025
- **Also known as:** GHSA-g99p-47x7-mq88, GO-2025-3990

## What is CVE-2025-59942?

CVE-2025-59942 is a high-severity vulnerability in filecoin-project go-f3, published on 29 Sep 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

go-f3 is a Golang implementation of Fast Finality for Filecoin (F3). In versions 0.8.6 and below, go-f3 panics when it validates a "poison" messages causing Filecoin nodes consuming F3 messages to become vulnerable. A "poison" message can can cause integer overflow in the signer index validation, which can cause the whole node to crash. These malicious messages aren't self-propagating since the bug is in the validator. An attacker needs to directly send the message to all targets. This issue is fixed in version 0.8.7.

Weakness: CWE-190 (Integer Overflow or Wraparound)

## Which versions are affected by CVE-2025-59942?

3 open source packages ship an affected version, including github.com/filecoin-project/go-f3. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/filecoin-project/go-f3` | Go | All versions | 0.8.7 |
| `github.com/filecoin-project/go-f3` | Go | All versions | 0.8.7 |
| `github.com/filecoin-project/go-f3` | Go | All versions | 0.8.7 |

Products: Filecoin Go-F3.

## How do I fix CVE-2025-59942?

Upgrade github.com/filecoin-project/go-f3 to 0.8.7 or later.

## Is CVE-2025-59942 being exploited?

There is no known exploitation of CVE-2025-59942 in the wild and no public exploit code.

## Other vulnerabilities in filecoin-project go-f3

- [CVE-2025-59941](https://insights.sbomify.com/CVE-2025-59941/): go-f3 is Vulnerable to Cached Justification Verification Bypass (medium 5.9)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-59942 and fix it if it is affected.

What it is: CVE-2025-59942 is a high-severity vulnerability in filecoin-project go-f3, published on 29 Sep 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 CVE-2025-59942 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/filecoin-project/go-f3 (Go): affected all versions; fixed in 0.8.7
- github.com/filecoin-project/go-f3 (Go): affected all versions; fixed in 0.8.7
- github.com/filecoin-project/go-f3 (Go): affected all versions; fixed in 0.8.7

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/CVE-2025-59942/ (Markdown: https://insights.sbomify.com/CVE-2025-59942/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-59942
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-59942
- OSV: https://osv.dev/vulnerability/CVE-2025-59942

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-59942/
Summaries are generated and may contain mistakes; the official description above is the record.