CVE-2024-39001 is a medium-severity (CVSS 6.3) CWE-1321 vulnerability in @ag-grid-enterprise/charts. A fix is available for @ag-grid-enterprise/charts — see the affected versions and patch details below.
ag-grid packages vulnerable to Prototype Pollution
Exploitation Status
Proof-of-concept exploit code exists
- CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.
Exploitation and automatability from CISA’s SSVC triage for CVE-2024-39001.
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
How urgent is this, really
CVE-2024-39001 plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.
Where this sits among everything scored
Of 378,567 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.
Real-World Exposure
How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.
@ag-grid-enterprise/chartsnpmag-grid-communitynpmag-grid-enterprisenpmDescription
ag-grid-enterprise v31.3.2 was discovered to contain a prototype pollution via the component _ModuleSupport.jsonApply. This vulnerability allows attackers to execute arbitrary code or cause a Denial of Service (DoS) via injecting arbitrary properties.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | @ag-grid-enterprise/charts | ≥ 32.0.0&&< 32.0.1 | 32.0.1npm install @ag-grid-enterprise/charts@32.0.1 |
| 📦npm | ag-grid-community | ≥ 32.0.0&&< 32.0.1 | 32.0.1npm install ag-grid-community@32.0.1 |
| 📦npm | ag-grid-enterprise | ≥ 32.0.0&&< 32.0.1 | 32.0.1npm install ag-grid-enterprise@32.0.1 |
| 📦npm | @ag-grid-enterprise/charts | all versions | 31.3.4npm install @ag-grid-enterprise/charts@31.3.4 |
| 📦npm | ag-grid-community | all versions | 31.3.4npm install ag-grid-community@31.3.4 |
| 📦npm | ag-grid-enterprise | all versions | 31.3.4npm install ag-grid-enterprise@31.3.4 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @ag-grid-enterprise/charts, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update @ag-grid-enterprise/charts to 32.0.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2024-39001 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2024-39001 can be triaged on real exposure rather than presence alone.
Tailored to CVE-2024-39001. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is CVE-2024-39001 in your dependencies?
O3 Security finds CVE-2024-39001 across npm dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.