CVE-2024-39014: utils · Prototype Pollution
Affects utilsSource CVE Database V5
Not known to be exploited · CVSS 9.8 Critical.
Data as of 26 Oct 2026, 17:16 UTC
- EPSS
- 0.6% chance of exploitation in 30 days – higher than 52% 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 1 Jul 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 26 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
npmcahil/utilspkg:npm/cahil/utilsOther 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
- Immediately audit all software dependencies to identify usage of ahilfoley cahil/utils version 2.3.2 or earlier.
- Monitor official sources and repositories for patches or updates addressing CVE-2024-39014 and apply them promptly once available.
- In the absence of patches, consider temporarily removing or replacing the vulnerable library with alternative utilities that do not exhibit prototype pollution vulnerabilities.
- Implement strict input validation and sanitization to prevent injection of malicious properties into objects, especially when handling untrusted data.
- Employ runtime application self-protection (RASP) or Web Application Firewalls (WAFs) configured to detect and block prototype pollution attack patterns.
- Conduct thorough code reviews focusing on object property assignments and usage of the set function to identify and remediate unsafe coding practices.
- Enhance logging and monitoring to detect unusual object mutations or application crashes indicative of exploitation attempts.
- Educate development teams about prototype pollution risks and secure coding standards to prevent recurrence.
Description
ahilfoley cahil/utils v2.3.2 was discovered to contain a prototype pollution via the function set. This vulnerability allows attackers to execute arbitrary code or cause a Denial of Service (DoS) via injecting arbitrary properties.