NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
📦
📦 npm
Not in CISA KEV
HIGH severity

Collection.js vulnerable to Prototype PollutionGHSA-47pj-q2vm-46xc

HIGHFix: kobezzza/Collection@d3d9376

GHSA-47pj-q2vm-46xc is a high-severity (CVSS 7.5) CWE-1321 vulnerability in collection.js. 2 public exploit or proof-of-concept references are indexed, so weaponization risk is real. A fix is available for collection.js — see the affected versions and patch details below.

Also known asCVE-2023-26113
Published
Updated
Affected
1 pkg
Patched
1 / 1
Exploits
2 known
Exploitation data as of Oct 26, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

Proof-of-concept exploit code exists

  • CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.

Exploitation and automatability from CISA’s SSVC triage for GHSA-47pj-q2vm-46xc.

EPSS Exploitation Probability

via FIRST.org ↗
1.2%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs68th percentile — riskier than 68% of all scored CVEsHighest risk
0.00%0.57%1.15%1.72%0.2%1.2%Apr 26Aug 26Oct 26

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

1 pkg affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.

12other npm packages depend on this — each one inherits the vulnerability until it's patched upstream
collection.jsnpm
504downloads / week

Description

Versions of the package collection.js before 6.8.1 are vulnerable to Prototype Pollution via the extend function in Collection.js/dist/node/iterators/extend.js.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
📦npmcollection.jsall versions6.8.1npm install collection.js@6.8.1

Affected Products

1 product · 1 configurations
Application
collection.jscollection.js_project
< 6.8.1
range
Exploits & PoCs
2

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

Versions of the package collection.js before 6.8.1 are vulnerable to Pro…

github.comNVDMar 2023

Report on security.snyk.io

security.snyk.ioNVDMar 2023

Detection & mitigation playbook

Open-source dependency

  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for collection.js, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update collection.js to 6.8.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-47pj-q2vm-46xc is resolved across your whole dependency graph.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

Versions of the package collection.js before 6.8.1 are vulnerable to Prototype Pollution via the `extend` function in `Collection.js/dist/node/iterators/extend.js`.
O3 Security · Impact-Aware SCA

Is GHSA-47pj-q2vm-46xc in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works
Collection.js vulnerable to Prototype Pollution (High 7.5)