Skip to main content
VulnerabilityPublished Updated

CVE-2024-39010: snapstate · Prototype Pollution

Affects snapstateSource CVE Database V5

0

Not known to be exploited · CVSS 9.8 Critical.

Data as of 26 Oct 2026, 13:47 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 59% 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
npmchase-moskal/snapstatepkg:npm/chase-moskal/snapstateOther threatsAffected
  • =0.0.9
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-39010, organizations should first verify if they are using snapstate v0.0.9 or any dependent software. 2) Implement strict input validation and sanitization to prevent malicious property names or values from being processed. 3) Employ JavaScript security best practices such as freezing prototypes (Object.freeze) or using libraries that prevent prototype pollution. 4) Isolate or sandbox components that use snapstate to limit the blast radius of potential exploitation. 5) Monitor application logs and runtime behavior for anomalies indicative of prototype pollution attacks, such as unexpected property changes or crashes. 6) Engage with the snapstate maintainers or community to track patch releases and apply updates promptly once available. 7) Consider temporary removal or replacement of snapstate if feasible until a secure version is released. 8) Educate development teams about prototype pollution risks and secure coding practices to prevent similar vulnerabilities in the future.

Description

chase-moskal snapstate v0.0.9 was discovered to contain a prototype pollution via the function attemptNestedProperty. This vulnerability allows attackers to execute arbitrary code or cause a Denial of Service (DoS) via injecting arbitrary properties.

References

Community reviews

Loading reviews…