CVE-2024-36582: object-deep-assign · n/a
Affects object-deep-assignSource CVE Database V5
Not known to be exploited · CVSS 9.8 Critical.
Data as of 25 Oct 2026, 19:02 UTC
- EPSS
- 0.5% chance of exploitation in 30 days – higher than 46% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 17 Jun 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
npmalexbinary/object-deep-assignpkg:npm/alexbinary/object-deep-assignOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
To mitigate CVE-2024-36582, organizations should first identify all instances where the object-deep-assign library version 1.0.11 is used, including transitive dependencies. Until an official patch is released, consider the following specific actions: 1) Replace or upgrade the vulnerable library with a patched or alternative library that does not suffer from prototype pollution issues. 2) Implement input validation and sanitization to prevent untrusted data from reaching the extend() method or similar functions that manipulate object properties. 3) Use JavaScript security best practices such as freezing or sealing objects to prevent prototype modifications where feasible. 4) Employ runtime application self-protection (RASP) or Web Application Firewalls (WAFs) with rules targeting prototype pollution attack patterns. 5) Monitor application logs and behavior for anomalies indicative of prototype pollution exploitation attempts. 6) Educate development teams about the risks of prototype pollution and secure coding practices to avoid similar vulnerabilities in custom code. 7) Maintain an inventory of dependencies and subscribe to vulnerability databases to promptly apply updates once patches become available.
Description
alexbinary object-deep-assign 1.0.11 is vulnerable to Prototype Pollution via the extend() method of Module.deepAssign (/src/index.js)