CVE-2024-39016: c3-utils-1 · Prototype Pollution
Affects c3-utils-1Source CVE Database V5
Not known to be exploited · CVSS 8.1 High.
Data as of 26 Oct 2026, 14:05 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:H/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 |
|---|---|---|
npmche3vinci/c3-utils-1pkg:npm/che3vinci/c3-utils-1Other 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-39016, organizations should first identify all instances of the che3vinci c3/utils-1 library version 1.0.131 within their software environments, including transitive dependencies. Since no official patches are currently available, consider the following specific actions: 1) Implement input validation and sanitization to prevent untrusted data from reaching the 'assign' function or similar object manipulation routines. 2) Employ runtime application self-protection (RASP) or web application firewalls (WAFs) configured to detect and block prototype pollution attack patterns. 3) Conduct thorough code reviews and static analysis focusing on object property assignments and prototype manipulations. 4) Isolate or sandbox components using this library to limit the blast radius of potential exploitation. 5) Monitor application logs and network traffic for unusual behaviors indicative of prototype pollution attempts. 6) Engage with the library maintainers or community to track patch releases and apply updates promptly once available. 7) Consider replacing or refactoring usage of the vulnerable library with safer alternatives if feasible. These targeted measures go beyond generic advice by focusing on the specific nature of prototype pollution and the affected library.
Description
che3vinci c3/utils-1 1.0.131 was discovered to contain a prototype pollution via the function assign. This vulnerability allows attackers to execute arbitrary code or cause a Denial of Service (DoS) via injecting arbitrary properties.