CVE-2026-58412

HIGHPre-NVD 8.28.2
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

This high-severity CVE scores 8.2 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2% (13th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source
Elevated

Also known asEUVD-2026-114446 (ENISA EUVD)Source: ENISA EUVD

8.2EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 8.2Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

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.

CVSS v3
8.2
EG Score
8.2HIGHmedium confidence
EG Risk
53
EG Risk 53/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity82% × 45%
Impact severity (EG Severity): CVSS 8.2 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.2%
EPSS %ILE
13th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (8.2): severity, escalated by confirmed exploitation. This CVE's 8.2 is its impact severity (EG Severity), not escalated.

EG Severity
8.2 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source · CVSS v3.0 or v3.1
EG Likelihood
0.2% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-12). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

October 30, 2026

Last Modified

November 6, 2026

Advisory Details (4)

Auto-updated Oct 30, 2026
🔬 Proof of concept available. Patch available. Sources: github_commit, github, github_pr.
Web page

GitHub - filecoin-project/filecoin-pin at v1.1.0 · GitHub

https://github.com/filecoin-project/filecoin-pin/tree/v1.1.0
GitHub commit Patch Available

commit 6fb9efd1796e (filecoin-project/filecoin-pin)

Patch available: filecoin-project/filecoin-pin v1.1.0 (contains commit 6fb9efd1796e)

https://github.com/filecoin-project/filecoin-pin/commit/6fb9efd1796e64a3515dffaa45b262e03cbd197c
GitHub pull request Patch Available

fix: detect fork-sourced workflow_run events before allowing Filecoin upload

Patch available: filecoin-project/filecoin-pin v1.1.0 (PR #588 merged 2026-06-18)

https://github.com/filecoin-project/filecoin-pin/pull/588
GitHub advisoryMentions a patch (unverified)🟡 PoC Available

Fork bypass in the privileged GitHub Actions workflow · Advisory · filecoin-project/filecoin-pin · GitHub

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

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 6× in last 7d / 14× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

  1. 2026-11-13 12:44 UTCEchelonGraph re-scored
  2. 2026-11-12 16:34 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  3. 2026-11-11 16:40 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  4. 2026-11-10 16:44 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  5. 2026-11-09 16:35 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  6. 2026-11-08 16:40 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  7. 2026-11-06 19:26 UTCEchelonGraph re-scored
  8. 2026-11-06 18:52 UTCEchelonGraph re-scored
  9. 2026-11-06 16:38 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  10. 2026-11-05 16:38 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  11. 2026-11-04 16:36 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  12. 2026-11-03 16:48 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  13. 2026-11-02 19:46 UTCEchelonGraph re-scored
  14. 2026-11-02 16:45 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  15. 2026-11-01 16:35 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  16. 2026-10-31 16:33 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  17. 2026-10-30 22:02 UTCENISA EUVD ID recordedEUVD-2026-114446 · Source: ENISA EUVD
  18. 2026-10-30 21:26 UTCEchelonGraph re-scored
  19. 2026-10-30 20:19 UTCEchelonGraph re-scoredFirst assessed: 8.2 HIGH
  20. 2026-10-30 20:18 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-58412?
CVE-2026-58412 is a high-severity vulnerability; its CVE record was published on October 30, 2026. 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…
When was the CVE record for CVE-2026-58412 published?
The CVE record for CVE-2026-58412 was published on October 30, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of November 6, 2026; the record at its source may have been updated since.
Is CVE-2026-58412 actively exploited?
CVE-2026-58412 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (13th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-58412?
CVE-2026-58412 has a CVSS base score of 8.2 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-58412?
A fix for CVE-2026-58412 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-58412

Explore →

Is Your Infrastructure Affected by CVE-2026-58412?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs