https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Sat, 03 Oct 2026 12:42:03 +0000 https://cve.radiocsirt.org/vuln/euvd-2026-253808 EUVD-2026-253808 https://cve.radiocsirt.org/vuln/euvd-2026-253808 https://cve.radiocsirt.org/vuln/fkie_cve-2025-59941 <p>go-f3 is a Golang implementation of Fast Finality for Filecoin (F3). In versions 0.8.8 and below, go-f3&#39;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&#39;s being used with. This issue is fixed in version 0.8.9.</p> <p>go-f3 is a Golang implementation of Fast Finality for Filecoin (F3). In versions 0.8.8 and below, go-f3&#39;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&#39;s being used with. This issue is fixed in version 0.8.9.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2025-59941 https://cve.radiocsirt.org/vuln/ghsa-7pq9-rf9p-wcrf <p><strong>Affected:</strong> Go: github.com/filecoin-project/go-f3</p> <p>### Description A vulnerability exists in go-f3&#39;s justification verification caching mechanism where verification results are cached without properly considering the context of the message. An attacker can bypass justification verification by: 1. First submitting a valid message with a correct justification 2. Then reusing the same cached justification in contexts where it would normally be invalid</p> <p>This occurs because the cached verification does not properly validate the relationship between the justification and the specific message context it&#39;s being used with.</p> <p>### Impact - Potential consensus integrity issues through invalid justification acceptance - Could affect network liveness if exploited systematically - May allow malicious actors to influence consensus decisions with invalid justifications - Requires significant power (350+ TiB due to power table rounding) to meaningfully exploit - It would also be difficult to exploit in a synchronised fashion, such that &gt;1/3 of the network goes down at one time. This isn&#39;t a one-msg panic, where you can spam it and bring everyone down, because every node will have a different amount of memory andmany SPs also run redundant lotus nodes.</p> <p>### Patches The fix was merged and released with go-f3 0.8.9. All node software (Lotus, Forest, Venus) are using a patched version of go-f3 with their updates for the nv27 network upgrade.</p> <p>### Workarounds The are no immediate workarounds available. Nodes should upgrade to the patched versio…</p> <p><strong>Affected:</strong> Go: github.com/filecoin-project/go-f3</p> <p>### Description A vulnerability exists in go-f3&#39;s justification verification caching mechanism where verification results are cached without properly considering the context of the message. An attacker can bypass justification verification by: 1. First submitting a valid message with a correct justification 2. Then reusing the same cached justification in contexts where it would normally be invalid</p> <p>This occurs because the cached verification does not properly validate the relationship between the justification and the specific message context it&#39;s being used with.</p> <p>### Impact - Potential consensus integrity issues through invalid justification acceptance - Could affect network liveness if exploited systematically - May allow malicious actors to influence consensus decisions with invalid justifications - Requires significant power (350+ TiB due to power table rounding) to meaningfully exploit - It would also be difficult to exploit in a synchronised fashion, such that &gt;1/3 of the network goes down at one time. This isn&#39;t a one-msg panic, where you can spam it and bring everyone down, because every node will have a different amount of memory andmany SPs also run redundant lotus nodes.</p> <p>### Patches The fix was merged and released with go-f3 0.8.9. All node software (Lotus, Forest, Venus) are using a patched version of go-f3 with their updates for the nv27 network upgrade.</p> <p>### Workarounds The are no immediate workarounds available. Nodes should upgrade to the patched versio…</p> https://cve.radiocsirt.org/vuln/ghsa-7pq9-rf9p-wcrf https://cve.radiocsirt.org/vuln/opensuse-su-2025:15666-1 <p>govulncheck-vulndb-0.0.20251023T162509-1.1 on GA media</p> <p>govulncheck-vulndb-0.0.20251023T162509-1.1 on GA media</p> https://cve.radiocsirt.org/vuln/opensuse-su-2025:15666-1