CVE-2025-59941

MediumCVSS 5.9

Published: 29/09/2025(UTC)Updated: 09/10/2026(UTC)Translated: 09/10/2026(UTC)NVD NIST

Exploitation Probability (EPSS)

Low risk

0.24%

14th percentile - higher than 14% of all known CVEs

Summary

go-f3 is a Golang implementation of Fast Finality for Filecoin (F3). In versions 0.8.8 and below, the justification verification caching mechanism caches verification results without properly considering the message context, allowing an attacker to bypass justification verification by reusing a cached justification in an invalid context.

Risk Assessment

An attacker can bypass justification verification, potentially leading to acceptance of invalid messages and undermining the integrity of F3 consensus.

Recommendation

Update go-f3 to version 0.8.9 or later, which fixes this issue.

Other vulnerabilities in go-f3

CVE-2025-59942High
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" message causing Filecoin nodes consuming F3 messages to become vulnerable. A "poison" message 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.

Original NVD description (English source)

go-f3 is a Golang implementation of Fast Finality for Filecoin (F3). In versions 0.8.8 and below, go-f3's justification verification caching mechanism has a vulnerability where verification results are cached without properly considering the context of the message. An attacker can bypass justification verification by submitting a valid message with a correct justification and then reusing the same cached justification in contexts where it would normally be invalid. This occurs because the cached verification does not properly validate the relationship between the justification and the specific message context it's being used with. This issue is fixed in version 0.8.9.

Vulnerability data from NVD (NIST) · CISA KEV · EPSS