GHSA-79xf-67r4-q2jj — safe-eval
CRITICALGHSA-79xf-67r4-q2jj is a critical-severity (CVSS 10) CWE-265 vulnerability in safe-eval. 8 public exploit references exist, so weaponization risk is real. No vendor fix is recorded yet; mitigation options are listed below.
safe-eval vulnerable to Sandbox Bypass due to improper input sanitization
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.
- A successful exploit gives an attacker total control of the affected component, not partial access.
Exploitation and automatability from CISA’s SSVC triage for GHSA-79xf-67r4-q2jj.
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-79xf-67r4-q2jj 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 379,145 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.
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, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
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 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-79xf-67r4-q2jj can be triaged on real exposure rather than presence alone.
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 Security finds GHSA-79xf-67r4-q2jj across npm dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.