VulnerabilityPublished 30 Oct 2026

CVE-2026-58412: filecoin-pin · Incorrect Authorization

Affects filecoin-pinSource CVE Database V5

Compare

Not known to be exploited · CVSS 8.2 High : upgrade to 1.1.0 soon.

Data as of 31 Oct 2026, 20:34 UTC

CVSS 3.1 base score

8.2High

How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none

CVSS scores by source
CNA (GitHub_M)	CVSS 3.1	8.2

EPSS: 0.2% chance of exploitation in 30 days – higher than 13% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 1.1.0

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:N/I:H/A:L

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: Required
Scope: Changed
Confidentiality: None
Integrity: High
Availability: Low

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: Required: Successful exploitation of this vulnerability requires a user to take some action before the vulnerability can be exploited.
Scope: Changed: An exploited vulnerability can affect resources beyond the security scope managed by the security authority of the vulnerable component. In this case, the vulnerable component and the impacted component are different and managed by different security authorities.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: High: There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the impacted component. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to the impacted component.
Availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the impacted component are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 30 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 31 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade filecoin-pin and filecoin-project/filecoin-pin to 1.1.0.

Affected software

Product	Affected	Fixed in
filecoin-projectfilecoin-pin	Affected <1.1.0	Fixed in 1.1.0
GitHubfilecoin-project/filecoin-pin`pkg:github/filecoin-project/filecoin-pin`Other threats	Affected <1.1.0	Fixed in 1.1.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade filecoin-pin to version 1.1.0 or later, where the fork detection logic in the GitHub Action upload workflow is corrected. The 0.x action line is not receiving a backport and must be migrated to the fixed 1.x release to remediate this vulnerability.

Description

CVE-2026-58412 is an authorization vulnerability in filecoin-project's filecoin-pin prior to version 1.1.0. The flaw arises from improper fork detection in the GitHub Action upload workflow, allowing an external contributor to cause attacker-controlled artifacts to be uploaded using the repository owner's Filecoin wallet. This leads to unauthorized storage costs, dataset pollution, and consumption of wallet funds without requiring disclosure of the wallet private key. The issue is fixed in version 1.1.0.

Impact

An attacker with the ability to create fork pull requests can cause artifacts they control to be uploaded using the repository owner's Filecoin wallet. This leads to unauthorized storage costs charged to the wallet, pollution of datasets, and consumption of wallet funds. The wallet private key itself is not disclosed or required to be disclosed for exploitation. The vulnerability has a CVSS v3.1 score of 8.2 (high severity) with no confidentiality impact but high integrity impact and low availability impact.

Summary

Filecoin Pin's GitHub Action upload workflow prior to version 1.1.0 improperly checks for fork pull requests by only inspecting the 'event.pull_request' field. In a two-workflow pattern, a privileged 'workflow_run' workflow downloads and uploads artifacts produced by an untrusted fork pull request. Since 'workflow_run' lacks 'event.pull_request', the fork detection fails, allowing the action to initialize the wallet with the repository owner's private key and upload attacker-controlled artifacts. This results in unauthorized use of the Filecoin wallet, incurring storage expenditure and dataset pollution. The vulnerability is classified as CWE-863 (Incorrect Authorization) and is resolved in version 1.1.0.

CWE-863Incorrect Authorization (opens in a new tab)
Class weaknessLikelihood of exploit: HighCWE Top 25 (2025): #17OWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The product performs an authorization check when an actor attempts to access a resource or perform an action, but it does not correctly perform the check.
Architecture and Design
Divide the product into anonymous, normal, privileged, and administrative areas. Reduce the attack surface by carefully mapping roles with data and functionality. Use role-based access control (RBAC) to enforce the roles at the appropriate boundaries.
Architecture and Design
Ensure that access control checks are performed related to the business logic. These checks may be different than the access control checks that are applied to more generic resources such as files, connections, processes, memory, and database records.
Architecture and Design · Libraries or Frameworks
Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
OWASP Cheat Sheets
Authorization (opens in a new tab)
OWASP ASVS 4.0.3
V8.3.8 (opens in a new tab)
V13.4.2 (opens in a new tab)
V7.2.2 (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 30 Oct 2026, 20:39 UTC

WeaknessesCWE-863

Technical details

References

Community reviews

Related threats