Prototype pollution via unfiltered __proto__ extension
Published Mar 18, 2023 · Updated Feb 26, 2025
Prototype pollution in Collection.js before 6.8.1 allows remote attackers to alter object prototypes through crafted extend input. The extend function in dist/node/iterators/extend.js copies an attacker-controlled proto key into the target object without filtering it. Exploitation requires a consuming application to pass attacker-controlled objects to extend, after which inherited properties become attacker-controlled.
Summary
What happened
Prototype pollution in Collection.js before 6.8.1 allows remote attackers to alter object prototypes through crafted extend input. The extend function in dist/node/iterators/extend.js copies an attacker-controlled proto key into the target object without filtering it. Exploitation requires a consuming application to pass attacker-controlled objects to extend, after which inherited properties become attacker-controlled.
The record
- CVE
- CVE-2023-26113
- Published
- Mar 18, 2023
- Updated
- Feb 26, 2025
- Vendor
- Collection.js Project
- Product
- Collection.js
- Classifications
- CWE-1321
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 18, 2023CVE publishedPublication date reported by the CVE source.
- Feb 26, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <6.8.1
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- Collection.js extend prototype-pollution proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo