Public vulnerability disclosure

CVE-2026-58412

Filecoin Pin: Fork bypass in the privileged GitHub Actions workflow

publishedCWE-863

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.

Technical severity8.2 highCVSS 3.1 · CNA: GitHub_M
Published2026-10-30Source updated 2026-11-06
Collected2026-11-064 attributed sources

Fixes and workarounds

Fix

filecoin-project/filecoin-pin/upload-action (actions): GitHub reports patched versions 1.1.0. Check the advisory for the affected release branch.

Source: GitHub GHSA-4rpx-vcp4-863j

Affected products and versions

Affected products, source version ranges and reporting authorities
ProductVersionsAuthority
filecoin-pin
filecoin-project
< 1.1.0 (affected) CNA: GitHub_M
filecoin-project/filecoin-pin/upload-action

filecoin-project/filecoin-pin/upload-action
actions
<=1.0.1 (affected, GitHub advisory range) GitHub GHSA-4rpx-vcp4-863j

Version ranges are source assertions. Check the vendor advisory and your installed configuration before determining exposure.

CVSS assessments

CVSS scores, vectors and reporting authorities
Version / scoreVectorAuthority
3.1 / 8.2
high
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:N/I:H/A:LCNA: GitHub_M
3.1 / 8.2
high
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:N/I:H/A:LNVD: [email protected]

Exploit evidence

No exploit evidence in collected sources. This is not proof of no exploitation.

References

For agents and automation

Read public disclosures for free as Markdown or JSON. Compatible browsers also expose native WebMCP tools to search disclosures, read this page, and discover API access.

Use the ontology-linked Cyber API with x402 pay per request, or a Y2 Pro or Elite API key with the intel:cyber scope.

Endpoints and access details

https://api.y2.dev/api/v2/cyber/cves
https://api.y2.dev/api/v2/cyber/cves/{cveId}

A workspace owner or admin can create a Pro or Elite API key. Send Authorization: Bearer <Y2_API_KEY> from your trusted agent runtime.

For x402, omit Authorization and read the HTTP 402 payment challenge before signing a retry. Public browser tools do not make payments.

Agent access JSON · OpenAPI · CVE API guide