VulnerabilityPublished 5 Nov 2026

CVE-2026-62300: filecoin-pin · Unbounded DAG pinning can exhaust server resources

Affects filecoin-pinSource GCVE Database

Compare

Authoritative record:CVE-2026-62300· Medium 6.5

Not known to be exploited · CVSS 6.5 Medium : upgrade to 1.1.1 when convenient.

Data as of 5 Nov 2026, 19:49 UTC

CVSS 3.1 base score

6.5Medium

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	6.5

Patch: Available – fixed in 1.1.1

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

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

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: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: High: There is total loss of availability, resulting in the attacker being able to fully deny access to resources in the impacted component; this loss is either sustained (while the attacker continues to deliver the attack) or persistent (the condition persists even after the attack has completed). Alternatively, the attacker has the ability to deny some availability, but the loss of availability presents a direct, serious consequence to the impacted component (e.g., the attacker cannot disrupt existing connections, but can prevent new connections; the attacker can repeatedly exploit a vulnerability that, in each instance of a successful attack, leaks a only small amount of memory, but after repeated exploitation causes a service to become completely unavailable).

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 5 Nov 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 to 1.1.1.

Affected software

Product	Affected	Fixed in
npmfilecoin-pin	Affected <1.1.1	Fixed in 1.1.1

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

AI-suggested

A patch is available in filecoin-pin version 1.1.1 that addresses this vulnerability. Users should upgrade to version 1.1.1 or later. The default configuration binds the server to localhost and requires an access token, which reduces exposure. Avoid enabling ALLOW_NO_AUTH=true in production environments. No additional mitigations are specified by the vendor advisory.

Description

filecoin-pin versions prior to 1.1.1 have an unbounded DAG pinning vulnerability where the Pinning Service API accepts user-controlled CIDs without enforcing limits on request rate, DAG size, or concurrency. This allows an attacker with authenticated access, or unauthenticated if no-auth mode is enabled, to cause resource exhaustion by recursively fetching large DAGs. The impact includes disk, network, CPU, and memory exhaustion leading to service degradation or failure. The default configuration limits exposure by binding to localhost and requiring an access token unless explicitly disabled. A fix is available in version 1.1.1.

Impact

Successful exploitation results in availability degradation due to unbounded resource consumption: disk exhaustion from large CAR files, network exhaustion from recursive Bitswap retrieval, CPU and memory pressure from concurrent pinning operations, and potential service or process failure affecting all users of the daemon. Operational costs and manual recovery efforts increase due to large partial CAR files. The risk is higher if the daemon is exposed beyond localhost, the access token is shared with untrusted users, or no-auth mode is enabled.

Summary

The IPFS Pinning Service API in filecoin-pin accepts a CID via POST /pins and queues background processing to recursively fetch the full DAG using helia.pins.add(cid). There are no enforced limits on request rate, per-user quota, DAG byte count, block count, traversal timeout, or concurrent pinning. An attacker can submit large DAGs, causing the server to consume excessive disk space (writing CAR files), network bandwidth (Bitswap retrieval), CPU, and memory (libp2p/Helia nodes). The Helia node created per pin does not bootstrap or use mDNS, but the API accepts origins, allowing attackers to supply reachable attacker-controlled libp2p nodes serving large DAGs. This leads to resource exhaustion and potential denial of service. The default daemon binds to localhost and requires an access token unless ALLOW_NO_AUTH=true is set, reducing exposure. The vulnerability is fixed in version 1.1.1.

CWE-400Uncontrolled Resource Consumption (opens in a new tab)
Class weaknessLikelihood of exploit: High
The product does not properly control the allocation and maintenance of a limited resource.
MITRE discourages mapping vulnerabilities to this broad entry; the root cause is usually a more specific weakness.
Architecture and Design
Design throttling mechanisms into the system architecture. The best protection is to limit the amount of resources that an unauthorized user can cause to be expended. A strong authentication and access control model will help prevent such attacks from occurring in the first place.
Architecture and Design
Mitigation of resource exhaustion attacks requires that the target system either: recognizes the attack and denies that user further access for a given amount of time, or; uniformly throttles all requests in order to make it more difficult to consume resources more quickly than they can again be freed.
Architecture and Design
Ensure that protocols have specific limits of scale placed on them.
OWASP Cheat Sheets
File Upload (opens in a new tab)
OWASP ASVS 4.0.3
V12.1.1 (opens in a new tab)
Attack patterns
XML Ping of the Death (opens in a new tab)
Regular Expression Exponential Blowup (opens in a new tab)
Sustained Client Engagement (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 5 Nov 2026, 19:49 UTC

WeaknessesCWE-400

Technical details

References

Community reviews

Related threats