GHSA-jxfh-8wgv-vfr2 is a high-severity (CVSS 7.7) Code Injection vulnerability in dojo. 1 public exploit reference exists, so weaponization risk is real. O3 Security confirms whether GHSA-jxfh-8wgv-vfr2 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
Prototype pollution in dojo
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.
dojonpmDescription
In affected versions of dojo (NPM package), the deepCopy method is vulnerable to Prototype Pollution.
Prototype Pollution refers to the ability to inject properties into existing JavaScript language construct prototypes, such as objects. An attacker manipulates these attributes to overwrite, or pollute, a JavaScript application object prototype of the base object by injecting other values.
This has been patched in versions 1.12.8, 1.13.7, 1.14.6, 1.15.3 and 1.16.2
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | dojo | all versions | 1.11.10 |
| 📦npm | dojo | ≥ 1.12.0&&< 1.12.8 | 1.12.8 |
| 📦npm | dojo | ≥ 1.13.0&&< 1.13.7 | 1.13.7 |
| 📦npm | dojo | ≥ 1.14.0&&< 1.14.6 | 1.14.6 |
| 📦npm | dojo | ≥ 1.15.0&&< 1.15.3 | 1.15.3 |
| 📦npm | dojo | ≥ 1.16.0&&< 1.16.2 | 1.16.2 |
Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for dojo. 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 dojo to 1.11.10 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-jxfh-8wgv-vfr2 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-jxfh-8wgv-vfr2 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-jxfh-8wgv-vfr2. 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-jxfh-8wgv-vfr2 in your dependencies?
O3 detects GHSA-jxfh-8wgv-vfr2 across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.