{"id":"EUVD-2026-114448","enisaUuid":"15bf86a5-42ce-3975-9715-4272a3724285","description":"Filecoin Pin is an IPFS Pinning Service API implementation that pins to Filecoin\u0027s PDP service. In daemon deployments up to and including version 1.1.0, `POST /pins` in `src/filecoin-pinning-server.ts` checks a caller-supplied CID with `CID.parse` and passes it to `pinStore.pin`, but does not enforce request rate limits or per-user quotas. In `src/filecoin-pin-store.ts`, each pin independently schedules `_processPinInBackground` with `setTimeout` without a queue, semaphore or concurrency cap, then recursively traverses the full DAG using `helia.pins.add(cid)`. The per-pin Helia/Bitswap node in `src/create-pinning-helia.ts` has no application-level byte, block or traversal-time limits. Blocks are written under `carStoragePath` by `src/core/car/car-blockstore-base.ts` and `src/core/car/car-file-backend.ts`, with `stats.totalSize` updated only after writing. An authenticated caller, or an anonymous caller when `ALLOW_NO_AUTH\u003dtrue`, can submit large DAGs and exhaust disk, network, CPU, memory and libp2p resources, causing service degradation or host/process failure and leaving partial CAR files requiring recovery. The default localhost binding and token requirement reduce exposure. Because nodes have no bootstrap or mDNS configuration, a CID alone may not be fetchable, but caller-supplied `origins` can point to a reachable attacker-controlled libp2p source; concurrent requests accelerate resource pressure. Version 1.1.1 documents operational mitigations but does not implement the missing resource controls.","datePublished":"Oct 30, 2026, 8:15:23 PM","dateUpdated":"Nov 2, 2026, 3:01:53 PM","baseScore":6.5,"baseScoreVersion":"3.1","baseScoreVector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H","references":"https://github.com/filecoin-project/filecoin-pin/security/advisories/GHSA-m5ph-mmg5-6w5h\nhttps://github.com/filecoin-project/filecoin-pin/commit/8db22b47899deb78dadf415fc477cae4bd6e82c2\n","aliases":"CVE-2026-62300\nGHSA-m5ph-mmg5-6w5h\n","assigner":"GitHub_M","epss":0.25,"enisaIdProduct":[{"id":"8802ea2e-c44f-3e31-8c23-bf37d5f04266","product":{"name":"filecoin-pin","vendor":{"name":"filecoin-project"}},"product_version":"≤ 1.1.0"}],"enisaIdVendor":[{"id":"92a9eaeb-3b56-3096-8ecc-85f196c86505","vendor":{"name":"filecoin-project"}}],"enisaIdVulnerability":[{"id":"b60649ef-7194-3f87-b86e-deb54ddeef83","vulnerability":{"id":"CVE-2026-62300","description":"Filecoin Pin is an IPFS Pinning Service API implementation that pins to Filecoin\u0027s PDP service. In daemon deployments up to and including version 1.1.0, `POST /pins` in `src/filecoin-pinning-server.ts` checks a caller-supplied CID with `CID.parse` and passes it to `pinStore.pin`, but does not enforce request rate limits or per-user quotas. In `src/filecoin-pin-store.ts`, each pin independently schedules `_processPinInBackground` with `setTimeout` without a queue, semaphore or concurrency cap, then recursively traverses the full DAG using `helia.pins.add(cid)`. The per-pin Helia/Bitswap node in `src/create-pinning-helia.ts` has no application-level byte, block or traversal-time limits. Blocks are written under `carStoragePath` by `src/core/car/car-blockstore-base.ts` and `src/core/car/car-file-backend.ts`, with `stats.totalSize` updated only after writing. An authenticated caller, or an anonymous caller when `ALLOW_NO_AUTH\u003dtrue`, can submit large DAGs and exhaust disk, network, CPU, memory and libp2p resources, causing service degradation or host/process failure and leaving partial CAR files requiring recovery. The default localhost binding and token requirement reduce exposure. Because nodes have no bootstrap or mDNS configuration, a CID alone may not be fetchable, but caller-supplied `origins` can point to a reachable attacker-controlled libp2p source; concurrent requests accelerate resource pressure. Version 1.1.1 documents operational mitigations but does not implement the missing resource controls.","datePublished":"Oct 30, 2026, 8:15:23 PM","dateUpdated":"Nov 2, 2026, 3:01:53 PM","status":"PUBLISHED","baseScore":6.5,"baseScoreVersion":"3.1","baseScoreVector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H","references":"https://github.com/filecoin-project/filecoin-pin/security/advisories/GHSA-m5ph-mmg5-6w5h\nhttps://github.com/filecoin-project/filecoin-pin/commit/8db22b47899deb78dadf415fc477cae4bd6e82c2\n","enisa_id":"EUVD-2026-114448\n","assigner":"GitHub_M","epss":0.25,"dataProcessed":"Nov 13, 2026, 7:19:04 AM","vulnerabilityProduct":[{"id":"cdf4a026-7855-3315-baab-c458e6d2d5c3","product":{"name":"filecoin-pin","vendor":{"name":"filecoin-project"}},"product_version":"≤ 1.1.0"}],"vulnerabilityVendor":[{"id":"c6f46712-1e92-33ec-b37f-cfe9c21f43d2","vendor":{"name":"filecoin-project"}}]}},{"id":"f58cd6dc-6371-37db-9b0b-577104c1032d","vulnerability":{"id":"GHSA-m5ph-mmg5-6w5h","description":"filecoin-pin: Unbounded DAG pinning can exhaust server resources","datePublished":"Nov 5, 2026, 6:07:30 PM","dateUpdated":"Nov 5, 2026, 6:07:30 PM","baseScore":0.0,"references":"https://github.com/filecoin-project/filecoin-pin/security/advisories/GHSA-m5ph-mmg5-6w5h\nhttps://nvd.nist.gov/vuln/detail/CVE-2026-62300\nhttps://github.com/filecoin-project/filecoin-pin/commit/8db22b47899deb78dadf415fc477cae4bd6e82c2\nhttps://github.com/filecoin-project/filecoin-pin/commit/afa019307db23a703737675e94316edcc6572050\nhttps://github.com/filecoin-project/filecoin-pin\nhttps://github.com/filecoin-project/filecoin-pin/releases/tag/v1.1.1\n","enisa_id":"EUVD-2026-114448\n","aliases":"CVE-2026-62300\nGHSA-m5ph-mmg5-6w5h\n","epss":0.0,"dataProcessed":"Nov 13, 2026, 7:06:32 AM","vulnerabilityProduct":[],"vulnerabilityVendor":[]}}],"enisaIdAdvisory":[]}