Skip to main content
VulnerabilityPublished Updated

CVE-2024-39017: agreejs shared · Code Injection

Source 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.6% chance of exploitation in 30 days – higher than 51% 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 1 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

AI-suggested

To mitigate CVE-2024-39017, organizations should first identify all instances of agreejs usage within their software stack, including indirect dependencies. Since no official patches are currently available, temporary mitigations include: 1) Avoid using or disable the mergeInternalComponents function if possible. 2) Implement strict input validation and sanitization to prevent injection of malicious properties. 3) Use security-focused JavaScript libraries that prevent prototype pollution or apply runtime checks to detect prototype modifications. 4) Employ application-level monitoring and anomaly detection to identify unusual object property changes or crashes indicative of exploitation attempts. 5) Isolate vulnerable components in sandboxed environments to limit potential damage. 6) Stay informed on vendor advisories and apply patches immediately once released. 7) Conduct code audits and penetration testing focused on prototype pollution vectors. 8) Educate developers about secure coding practices to avoid unsafe object merges. These steps help reduce the attack surface and protect against exploitation until a formal patch is available.

Description

agreejs shared v0.0.1 was discovered to contain a prototype pollution via the function mergeInternalComponents. This vulnerability allows attackers to execute arbitrary code or cause a Denial of Service (DoS) via injecting arbitrary properties.

References

Community reviews

Loading reviews…