Skip to main content
VulnerabilityPublished Updated

CVE-2024-38984: json-override · Prototype Pollution

Affects json-overrideSource CVE Database V5

0

Not known to be exploited · CVSS 9.8 Critical.

Data as of 26 Oct 2026, 14:05 UTC

CVSS 3.1 base score
9.8Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.9% chance of exploitation in 30 days – higher than 61% 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:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 30 Jul 2024

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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

ProductAffectedFixed in
npmjson-overridepkg:npm/json-overrideOther threatsAffected
  • =0.2.0
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-38984, organizations should immediately audit their software dependencies to identify usage of json-override version 0.2.0. Until an official patch is released, consider the following specific actions: 1) Remove or replace json-override with alternative libraries that do not have prototype pollution vulnerabilities. 2) Implement input validation and sanitization to block or filter out payloads attempting to manipulate the __proto__ property. 3) Employ runtime security tools such as Node.js security modules or application firewalls that detect and prevent prototype pollution attacks. 4) Monitor application logs and network traffic for suspicious activity indicative of prototype pollution exploitation attempts. 5) Apply strict Content Security Policies (CSP) and sandboxing where applicable to limit the impact of potential code execution. 6) Stay updated with vendor advisories and apply patches promptly once available. 7) Conduct security testing, including fuzzing and static analysis, focusing on prototype pollution vectors. These targeted mitigations go beyond generic advice by focusing on the unique aspects of prototype pollution and the specific library involved.

Description

Prototype Pollution in lukebond json-override 0.2.0 allows attackers to to execute arbitrary code or cause a Denial of Service (DoS) via the __proto__ property.

References

Community reviews

Loading reviews…