GHSA-328p-362g-r48j is a medium-severity (CVSS 6.3) CWE-1321 vulnerability in @ag-grid-enterprise/charts. O3 Security confirms whether GHSA-328p-362g-r48j is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
ag-grid packages vulnerable to Prototype Pollution
Real-World Exposure
How broadly this vulnerability is actually deployed: weekly install volume shows current usage, a proxy for how much of the ecosystem is exposed.
@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.1 |
| 📦npm | ag-grid-community | ≥ 32.0.0&&< 32.0.1 | 32.0.1 |
| 📦npm | ag-grid-enterprise | ≥ 32.0.0&&< 32.0.1 | 32.0.1 |
| 📦npm | @ag-grid-enterprise/charts | all versions | 31.3.4 |
| 📦npm | ag-grid-community | all versions | 31.3.4 |
| 📦npm | ag-grid-enterprise | all versions | 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. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
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 GHSA-328p-362g-r48j 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 pinpoints whether GHSA-328p-362g-r48j is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to GHSA-328p-362g-r48j. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-328p-362g-r48j in your dependencies?
O3 detects GHSA-328p-362g-r48j across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.