Skip to content

go-f3 module vulnerable to integer overflow leading to panic

High severity GitHub Reviewed Published Sep 29, 2025 in filecoin-project/go-f3 • Updated Sep 30, 2025

Package

gomod github.com/filecoin-project/go-f3 (Go)

Affected versions

< 0.8.7

Patched versions

0.8.7

Description

Impact

Filecoin nodes consuming F3 messages are vulnerable. go-f3 panics when it validates a "poison" messages. A "poison" message can can cause integer overflow in the signer index validation. In Lotus' case, the whole node will crash.

There is no barrier to entry. An attacker doesn't need any power to pull off this attack.

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.

Patches

The fix was merged and released with go-f3 0.8.7. All node software (Lotus, Forest, Venus) are using a patched version of go-f3 with their updates for the nv27 network upgrade.

go-f3 now does proper overflow checking using math.MaxInt64 comparison and returns error "justificationPower overflow" when overflow would occur.

Workarounds

The are no immediate workarounds available. Nodes should upgrade to the patched version, which they will have done if participating in nv27 on Filecoin mainnet.

Credits

The initial finding(unrelated path) was reported by 0xNirix via bug bounty program which wasn't high issue. The further digging by developers led to this finding. Thank you for the contributions.

References

@parthshah1 parthshah1 published to filecoin-project/go-f3 Sep 29, 2025
Published to the GitHub Advisory Database Sep 29, 2025
Reviewed Sep 29, 2025
Published by the National Vulnerability Database Sep 29, 2025
Last updated Sep 30, 2025

Severity

High

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

EPSS score

Exploit Prediction Scoring System (EPSS)

This score estimates the probability of this vulnerability being exploited within the next 30 days. Data provided by FIRST.
(16th percentile)

Weaknesses

Integer Overflow or Wraparound

The product performs a calculation that can produce an integer overflow or wraparound, when the logic assumes that the resulting value will always be larger than the original value. This can introduce other weaknesses when the calculation is used for resource management or execution control. Learn more on MITRE.

CVE ID

CVE-2025-59942

GHSA ID

GHSA-g99p-47x7-mq88

Source code

Credits

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.