CVE-2024-36580: cdr0 · n/a
Affects cdr0Source CVE Database V5
Not known to be exploited · CVSS 9.8 Critical.
Data as of 26 Oct 2026, 06:26 UTC
- EPSS
- 0.7% chance of exploitation in 30 days – higher than 55% 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-26.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
npmcdr0pkg:npm/cdr0Other 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
Until an official patch is released, organizations should implement the following mitigations: 1) Restrict network access to cdr0 sg services using firewalls or network segmentation to limit exposure to untrusted sources. 2) Employ runtime application self-protection (RASP) or web application firewalls (WAF) with custom rules to detect and block suspicious prototype pollution payloads. 3) Conduct thorough code reviews and static analysis to identify and remediate unsafe object prototype manipulations in custom integrations or extensions. 4) Monitor logs and network traffic for unusual activity indicative of exploitation attempts. 5) Prepare incident response plans specifically addressing potential exploitation scenarios. 6) Stay updated with vendor advisories and apply patches immediately upon availability. 7) Consider temporary disabling or isolating vulnerable instances if feasible to reduce risk. These steps go beyond generic advice by focusing on network-level controls, detection, and proactive code hygiene.
Description
A Prototype Pollution issue in cdr0 sg 1.0.10 allows an attacker to execute arbitrary code.