{"answers":{"affected":"3 open source packages ship an affected version, including github.com/filecoin-project/go-f3. It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-59941 in the wild and no public exploit code.","fix":"Upgrade github.com/filecoin-project/go-f3 to 0.8.9 or later.","what":"CVE-2025-59941 is a medium-severity vulnerability in filecoin-project go-f3, published on 29 Sep 2025. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-59941 and fix it if it is affected.\n\nWhat it is: CVE-2025-59941 is a medium-severity vulnerability in filecoin-project go-f3, published on 29 Sep 2025. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2025-59941 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- github.com/filecoin-project/go-f3 (Go): affected all versions; fixed in 0.8.9\n- github.com/filecoin-project/go-f3 (Go): affected all versions; fixed in 0.8.9\n- github.com/filecoin-project/go-f3 (Go): affected all versions; fixed in 0.8.9\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2025-59941/ (Markdown: https://insights.sbomify.com/CVE-2025-59941/index.md)","id":"CVE-2025-59941","markdown":"https://insights.sbomify.com/CVE-2025-59941/index.md","name":"CVE-2025-59941","record":{"aliases":["GHSA-7pq9-rf9p-wcrf","GO-2025-3989"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Go Filecoin library","requires_auth":"low_privilege","summary":"An attacker can bypass justification verification in go-f3 by reusing cached verification results across different message contexts.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"go-f3","vendor":"filecoin"}],"cvss":{"score":5.9,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:H/A:L","version":"3.1"},"cwes":[{"id":"CWE-305","name":"Authentication Bypass by Primary Weakness"}],"description":"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.","ecosystems":["Go"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"go-f3 is Vulnerable to Cached Justification Verification Bypass","id":"CVE-2025-59941","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Go","product":null,"products":[],"type":"security_feature_bypass","year":"2025"},"n_packages":3,"n_references":2,"next":{"headline":"go-f3 module vulnerable to integer overflow leading to panic","id":"CVE-2025-59942"},"packages":[{"ecosystem":"Go","fixed":["0.8.9"],"introduced":["0"],"last_affected":[],"package":"github.com/filecoin-project/go-f3","purl":null,"source":"GHSA-7pq9-rf9p-wcrf"},{"ecosystem":"Go","fixed":["0.8.9"],"introduced":["0"],"last_affected":[],"package":"github.com/filecoin-project/go-f3","purl":"pkg:golang/github.com/filecoin-project/go-f3","source":"GHSA-7pq9-rf9p-wcrf"},{"ecosystem":"Go","fixed":["0.8.9"],"introduced":["0"],"last_affected":[],"package":"github.com/filecoin-project/go-f3","purl":"pkg:golang/github.com/filecoin-project/go-f3","source":"GO-2025-3989"}],"prev":{"headline":"mkdocs-include-markdown-plugin susceptible to unvalidated input colliding with substitution placeholders","id":"CVE-2025-59940"},"products":["go-f3"],"published":"2025-09-29","related":[{"cvss_score":7.5,"headline":"go-f3 module vulnerable to integer overflow leading to panic","id":"CVE-2025-59942","kev_date_added":null,"published":"2025-09-29"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CC BY 4.0","name":"Go Vulnerability Database","prefix":"GO"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-09-30","vendors":["filecoin-project"]},"summary":"An attacker can bypass justification verification in go-f3 by reusing cached verification results across different message contexts.","url":"https://insights.sbomify.com/CVE-2025-59941/"}