GHSA-m8gw-hjpr-rjv7
HIGHGHSA-m8gw-hjpr-rjv7 is a high-severity (CVSS 7.5) CWE-1321 vulnerability in dojo. 5 public exploit references exist, so weaponization risk is real. O3 Security confirms whether GHSA-m8gw-hjpr-rjv7 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
Prototype Pollution in dojo
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
GHSA-m8gw-hjpr-rjv7 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 365,950 CVEs with a current EPSS score, this one falls in the 10–50% 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.
dojonpmDescription
All versions of package dojo are vulnerable to Prototype Pollution via the setObject function.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | dojo | all versions | No fix |
Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.
All versions of package dojo are vulnerable to Prototype Pollution via t…
All versions of package dojo are vulnerable to Prototype Pollution via t…
All versions of package dojo are vulnerable to Prototype Pollution via t…
All versions of package dojo are vulnerable to Prototype Pollution via t…
All versions of package dojo are vulnerable to Prototype Pollution via t…
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.
Remediation status
No patched version of dojo has shipped for GHSA-m8gw-hjpr-rjv7 yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.
Mitigate without a patch
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-m8gw-hjpr-rjv7 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-m8gw-hjpr-rjv7. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Fixing This On Your OS
If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.
Frequently Asked Questions
Is GHSA-m8gw-hjpr-rjv7 in your dependencies?
O3 detects GHSA-m8gw-hjpr-rjv7 across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.