CVE-2026-58412

Filecoin Pin: Fork bypass in the privileged GitHub Actions workflow

Published Oct 30, 2026 CVSS 3.1 · 8.2 High EPSS < 1% KEV · Not listed
Description
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.

Analysis

AI-generated

Technical impact

The vulnerability lies in the Filecoin Pin upload GitHub Action, where the fork‑detection logic only inspects the event.pull_request field of the initial pull‑request trigger. A privileged workflow_run that lacks this field incorrectly marks the source as not a fork, allowing the action to initialize a wallet with the repository owner’s private key and upload attacker‑controlled artifacts. As a result, the repository owner’s Filecoin wallet is used to store unwanted data, incurring storage costs, polluting the dataset, and draining configured funds without requiring disclosure of the private key.

Affected Systems

All instances of filecoin-project/filecoin-pin before release 1.1.0 are affected, as the flaw exists in the upload‑action tooling bundled with those releases.

Risk and Exploitability

Based on the description, it is inferred that attackers can exploit the flaw by creating a forked pull request that triggers the privileged workflow_run, bypassing fork checks and uploading malicious artifacts. With a CVSS score of 8.2 the vulnerability is high severity. Although EPSS is not available, the public nature of GitHub Actions and the ability for an external contributor to create a forked pull request make exploitation straightforward. The flaw is not yet listed in KEV, but attackers can trigger the privileged workflow_run to use the stored wallet credentials and spend the owner’s resources. The risk is therefore significant for any repository maintaining the vulnerable action and not restricting forked workflows.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade Filecoin Pin to version 1.1.0 or later, which corrects the fork‑checking logic in the upload action.
  • Reconfigure the workflow to restrict the privileged workflow_run event so it does not execute on forks, and add a re‑validation of the fork status before initializing the wallet.
  • Implement artifact validation or a credential check to ensure only trusted files are uploaded, and monitor the Filecoin wallet for anomalous storage transactions.

Generated by OpenCVE AI on October 30, 2026 at 21:56 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'poc', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
First Time appeared Filecoin-project
Filecoin-project filecoin-pin
Vendors & Products Filecoin-project
Filecoin-project filecoin-pin
Type Values Removed Values Added
Description 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.
Title Filecoin Pin: Fork bypass in the privileged GitHub Actions workflow
Weaknesses CWE-863
References
Metrics cvssV3_1

{'score': 8.2, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:N/I:H/A:L'}

Weaknesses

Sources

Status
PUBLISHED
Assigner
GitHub_M
Published
Updated
Nov 6, 2026, 6:48 PM
Reserved
Jun 30, 2026, 6:19 PM
Status
Deferred
Published
Oct 30, 2026, 9:17 PM
Modified
Nov 6, 2026, 7:17 PM