filecoin-project go-f3 up to 0.8.8 Message authentication bypass

Summaryinfo

A vulnerability marked as problematic has been reported in filecoin-project go-f3 up to 0.8.8. Affected by this vulnerability is an unknown functionality of the component Message Handler. Performing a manipulation results in authentication bypass. This vulnerability is reported as CVE-2025-59941. The attack is possible to be carried out remotely. No exploit exists. It is suggested to upgrade the affected component.

Detailsinfo

A vulnerability was found in filecoin-project go-f3 up to 0.8.8. It has been classified as problematic. This affects an unknown code of the component Message Handler. The manipulation with an unknown input leads to a authentication bypass vulnerability. CWE is classifying the issue as CWE-305. The authentication algorithm is sound, but the implemented mechanism can be bypassed as the result of a separate weakness that is primary to the authentication error. This is going to have an impact on integrity, and availability. The summary by CVE is:

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.

The advisory is shared at github.com. This vulnerability is uniquely identified as CVE-2025-59941 since 09/23/2025. The exploitability is told to be difficult. It is possible to initiate the attack remotely. Neither technical details nor an exploit are publicly available.

Upgrading to version 0.8.9 eliminates this vulnerability. Applying the patch 76fff18cf07b21baccf537024bdb2fb41f75f6e2 is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Productinfo

Type

• Project Management Software

Vendor

• filecoin-project

Name

• go-f3

Version

• 0.8.0
• 0.8.1
• 0.8.2
• 0.8.3
• 0.8.4
• 0.8.5
• 0.8.6
• 0.8.7
• 0.8.8

License

• open-source

Website

• Product: https://github.com/filecoin-project/go-f3/

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Discussion