CVE-2026-58412

HighCVSS 8.2

Published: 30/10/2026(UTC)Updated: 02/11/2026(UTC)Translated: 30/10/2026(UTC)NVD NIST

Exploitation Probability (EPSS)

Low risk

0.23%

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

Summary

Filecoin Pin before version 1.1.0 has flawed fork detection in the GitHub upload action, which only checks event.pull_request. In the two-workflow pattern, workflow_run lacks this event, so isForkPR is false and an artifact from an untrusted fork is uploaded using the repository owner's wallet. An external contributor can cause unauthorized Filecoin wallet expenditure.

Risk Assessment

An attacker can consume the repository owner's Filecoin wallet funds, pollute datasets, and exhaust configured funds. Disclosure of the wallet private key is not required.

Recommendation

Update Filecoin Pin to version 1.1.0 or later. The 0.x line will not receive a backport and must be migrated to 1.x.

Other vulnerabilities in Filecoin Pin

CVE-2026-62300Medium
Filecoin Pin up to and including version 1.1.0 does not enforce request rate limits or per-user quotas on POST /pins, and each pin is processed in the background without a queue or concurrency cap. Missing byte, block and traversal-time limits allow an authenticated caller, or an anonymous caller when ALLOW_NO_AUTH=true, to exhaust disk, network, CPU, memory and libp2p resources, causing service degradation or host/process failure and leaving partial CAR files requiring recovery.

Original NVD description (English source)

Filecoin Pin is an IPFS Pinning Service API implementation that pins to Filecoin's PDP service. Prior to 1.1.0, the upload GitHub Action's fork detection in `upload-action/src/build.js` checks only `event.pull_request`. In the documented two-workflow pattern, an untrusted fork pull-request workflow produces an artifact and a privileged `workflow_run` workflow downloads and uploads it. Because `workflow_run` has no `event.pull_request`, `isForkPR` becomes false and `uploadStatus` becomes `pending-upload`. The action later resolves `workflow_run.pull_requests` without repeating the fork check before initializing the wallet with `walletPrivateKey` and uploading the artifact. An external contributor can therefore cause attacker-controlled artifacts to be stored using the repository owner's Filecoin wallet, incurring unauthorized storage expenditure, dataset pollution and consumption of configured wallet funds. Disclosure of the wallet private key is not required. The 0.x action line is not receiving a backport and must be migrated to a fixed 1.x release. This issue is fixed in version 1.1.0.

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