Skip to main content
CVE-2024-38991VulnerabilityPublished Updated

CVE-2024-38991: n/a

Source CVE Database V5

0

Not known to be exploited · CVSS 8.8 High.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score
8.8High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.8% chance of exploitation in 30 days – higher than 57% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:L/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 2026-10-25.

What to do

AI-suggested

To mitigate CVE-2024-38991, organizations should first identify all instances of the akbr patch-into library version 1.0.1 within their software environments. Since no official patches are currently linked, developers should consider the following steps: 1) Implement input validation and sanitization to prevent untrusted data from reaching the patchInto function. 2) Employ runtime application self-protection (RASP) or Web Application Firewalls (WAFs) configured to detect and block prototype pollution attack patterns. 3) Isolate or sandbox components using this library to limit the impact of potential exploitation. 4) Monitor application logs and behavior for anomalies indicative of prototype pollution attacks. 5) Engage with the library maintainers or community to track the release of official patches and apply them promptly once available. 6) Conduct thorough code reviews and security testing focusing on prototype pollution vectors in JavaScript dependencies. These targeted actions go beyond generic advice and address the specific nature of this vulnerability.

Description

akbr patch-into v1.0.1 was discovered to contain a prototype pollution via the function patchInto. This vulnerability allows attackers to execute arbitrary code or cause a Denial of Service (DoS) via injecting arbitrary properties.

References

Community reviews

Loading reviews…