filecoin-pin: Unbounded DAG pinning can exhaust server resources

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

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

EPSS

• CVE-2026-62300: 0.25% estimated exploitation activity in the next 30 days; percentile 16.31 (FIRST EPSS, 2026-11-10). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Summary The IPFS Pinning Service API implementation accepts a caller-controlled CID through `POST /pins`, queues background processing, and then recursively fetches the full DAG with `helia.pins.add(cid)`. The route and background pinning path do not enforce a request rate limit, per-user quota, maximum DAG byte count, maximum block count, traversal timeout, or concurrent pinning limit. An authenticated caller, or an unauthenticated caller when the server is started with `ALLOW_NO_AUTH=true`, can submit one or more pins whose CIDs resolve to very large DAGs. The server writes fetched blocks to CAR files under `carStoragePath` and can consume disk, network, CPU, and libp2p resources until the process or host becomes unavailable.

Details `POST /pins` validates only that the request body contains a syntactically valid CID string, then forwards it to the pin store: - `src/filecoin-pinning-server.ts:304-342` accepts the request, parses `cid` with `CID.parse`, and calls…

Published by the source

5 Nov 2026, 18:07 UTC

Last modified by the source

5 Nov 2026, 18:15 UTC

Source last checked

6 Nov 2026, 06:00 UTC

1. Revision 2 · amended · 6 Nov 2026

   Amended from osv record GHSA-m5ph-mmg5-6w5h

2. Revision 1 · created · 5 Nov 2026

   Published from ghsa record GHSA-m5ph-mmg5-6w5h

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-62300

Advisory: filecoin-pin: Unbounded DAG pinning can exhaust server resources
IDs: CVE-2026-62300, GHSA-m5ph-mmg5-6w5h
Record: https://patchnext.com/advisories/cve-2026-62300 (revision 2, source checked 6 Nov 2026, 06:00 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 6.5)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: filecoin-pin 1.1.1. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm filecoin-pin: affected < 1.1.1; fixed in 1.1.1

## Suggested inspection (read-only)
- `npm ls filecoin-pin --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on filecoin-pin.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-m5ph-mmg5-6w5h (GitHub-reviewed advisory GHSA-m5ph-mmg5-6w5h lists affected ranges: npm filecoin-pin >=0 <=1.1.0)
- Verified: https://osv.dev/vulnerability/GHSA-m5ph-mmg5-6w5h (OSV record GHSA-m5ph-mmg5-6w5h lists affected ranges: npm filecoin-pin >=0 <1.1.1 (fixed))

Commands are suggestions: review each one before running it.