Live › vulnerability › CVE-2026-58412
The Filecoin Pin upload GitHub Action skips its fork check in workflow_run runs, so artifacts from an outside pull request get uploaded. An external contributor can make those uploads run on the repository owner's Filecoin wallet, spending its funds and storing attacker-chosen data.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-30 21:25 UTC. All times on this page are UTC.
Repositories that run the Filecoin Pin upload action in a two-workflow setup, where an untrusted pull_request workflow produces an artifact and a privileged workflow_run workflow uploads it with a wallet key. Workflows that only run on direct pushes or do not hold a Filecoin wallet key are not exposed. Repositories already on a fixed 1.x release are not affected.
No product ranges from the sources yet.
uses: .../[email protected] or a 1.x tag.workflow_run trigger that downloads an artifact produced by a pull_request workflow and then calls the upload action with walletPrivateKey.1.1.0 or later.Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
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.
This page as .md · .json · in your agent: get_signal("CVE-2026-58412")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.