filecoin-project vulnerabilities and threats

CVE-2026-62300 is a resource exhaustion vulnerability in filecoin-pin up to version 1.1.0. The service does not enforce rate limits or quotas on pinning requests, allowing authenticated or anonymous users (if configured) to submit large DAGs that exhaust disk, network, CPU, memory, and libp2p resources. This can degrade service or cause process failure, leaving partial CAR files that require recovery. Default localhost binding and token requirements reduce exposure. Version 1.1.1 documents mitigations but does not implement resource controls.

CVE-2026-58412 is an authorization vulnerability in filecoin-project's filecoin-pin prior to version 1.1.0. The flaw arises from improper fork detection in the GitHub Action upload workflow, allowing an external contributor to cause attacker-controlled artifacts to be uploaded using the repository owner's Filecoin wallet. This leads to unauthorized storage costs, dataset pollution, and consumption of wallet funds without requiring disclosure of the wallet private key. The issue is fixed in version 1.1.0.

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

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.