Skip to main content
VulnerabilityPublished Updated

CVE-2024-38996: ag-grid-community · Prototype Pollution

Affects ag-grid-communitySource CVE Database V5

0

Not known to be exploited · CVSS 9.8 Critical.

Data as of 26 Oct 2026, 17:16 UTC

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

Affected software

ProductAffectedFixed in
npmag-grid-communitypkg:npm/ag-grid-communityOther threatsAffected
  • =31.3.2
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-38996, organizations should immediately identify all instances of ag-grid-community and ag-grid-enterprise version 31.3.2 in their environments. In the interim, consider the following specific mitigations: 1) Implement strict input validation and sanitization on all data passed to the _.mergeDeep function or any object merging utilities to prevent injection of malicious properties. 2) Employ runtime application self-protection (RASP) or Web Application Firewall (WAF) rules to detect and block suspicious payloads attempting prototype pollution patterns. 3) Restrict network exposure of applications using vulnerable ag-grid versions to trusted internal networks where possible. 4) Conduct thorough code reviews and static analysis to identify unsafe object merges or prototype manipulations in custom code. 5) Use Content Security Policy (CSP) headers to limit the impact of potential code execution. 6) Prepare incident response plans to quickly address any signs of exploitation. Once a vendor patch is released, prioritize immediate application of updates across all affected systems to fully remediate the vulnerability.

Description

ag-grid-community v31.3.2 and ag-grid-enterprise v31.3.2 were discovered to contain a prototype pollution via the _.mergeDeep function. This vulnerability allows attackers to execute arbitrary code or cause a Denial of Service (DoS) via injecting arbitrary properties.

References

Community reviews

Loading reviews…