GHSA-79xf-67r4-q2jj
CRITICALsafe-eval vulnerable to Sandbox Bypass due to improper input sanitization
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.
Blast Radius
Weekly download volume for affected packages — a proxy for how broadly this vulnerability is deployed.
safe-evalnpmDescription
All versions of the package safe-eval are vulnerable to Sandbox Bypass due to improper input sanitization. The vulnerability is derived from prototype pollution exploitation. Exploiting this vulnerability might result in remote code execution (RCE).
Vulnerable functions:
defineGetter, stack(), toLocaleString(), propertyIsEnumerable.call(), valueOf().
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | safe-eval | 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 the package safe-eval are vulnerable to Sandbox Bypass d…
All versions of the package safe-eval are vulnerable to Sandbox Bypass d…
All versions of the package safe-eval are vulnerable to Sandbox Bypass d…
All versions of the package safe-eval are vulnerable to Sandbox Bypass d…
All versions of the package safe-eval are vulnerable to Sandbox Bypass d…
All versions of the package safe-eval are vulnerable to Sandbox Bypass d…
All versions of the package safe-eval are vulnerable to Sandbox Bypass d…
All versions of the package safe-eval are vulnerable to Sandbox Bypass d…
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for safe-eval. 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 safe-eval has shipped for GHSA-79xf-67r4-q2jj 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-79xf-67r4-q2jj 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-79xf-67r4-q2jj. 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-79xf-67r4-q2jj in your dependencies?
O3 detects GHSA-79xf-67r4-q2jj across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.