Skip to main content
CVE-2024-39011VulnerabilityPublished Updated

CVE-2024-39011: chargeover-redoc · n/a

Affects chargeover-redocSource CVE Database V5

0

Not known to be exploited · CVSS 9.8 Critical.

Data as of 26 Oct 2026, 06:26 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 60% 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 2026-10-26.

What to do

Affected software

ProductAffectedFixed in
npmchargeover-redocpkg:npm/chargeover-redocOther threatsAffected
  • =2.0.9-rc.69
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

1. Immediately audit and inventory all instances of chargeover redoc v2.0.9-rc.69 within your environment. 2. Restrict network exposure of affected services by implementing firewall rules or network segmentation to limit access to trusted users only. 3. Employ runtime application self-protection (RASP) or web application firewalls (WAF) with custom rules to detect and block suspicious payloads attempting prototype pollution attacks. 4. Monitor application logs and network traffic for anomalous behavior indicative of prototype pollution exploitation attempts, such as unusual object property modifications or crashes. 5. Engage with the software vendor or community to obtain patches or updates as soon as they become available and prioritize their deployment. 6. Consider temporary mitigations such as input validation and sanitization around the mergeObjects function if source code access is possible. 7. Educate development teams about prototype pollution risks and secure coding practices to prevent similar vulnerabilities in future releases.

Description

Prototype Pollution in chargeover redoc v2.0.9-rc.69 allows attackers to execute arbitrary code or cause a Denial of Service (DoS) and cause other impacts via the function mergeObjects.

References

Community reviews

Loading reviews…