safe-eval Known Vulnerabilities & Fixes
safe-eval has 2 known security vulnerabilities in npm (Node.js). Review the table below for affected and fixed versions. Data sourced from OSV, enriched with EPSS exploit probability and CISA KEV.
Low Immediate Risk
No actively exploited vulnerabilities detected. Monitor and update in your next maintenance window.
Is safe-eval in your project?
Check if you're affected by these 2 vulnerabilities.
Security Summary
- 2 affected version ranges have been identified across these 2 advisories.
- 0% of known issues have a published fixed version.
- Remediation: npm update safe-eval
Vulnerabilities
2 unique vulnerabilities — sorted by exploitation risk (KEV → EPSS → CVSS). Click a CVE/GHSA ID for full details.
| CVE / GHSA | Severity | Affected | Fixed In |
|---|---|---|---|
| CVE-2023-26122 safe-eval vulnerable to Sandbox Bypass due to improper input sanitization | CRITICAL | All versions | No fix available |
| CVE-2023-26121 safe-eval vulnerable to Prototype Pollution via the safeEval function | CRITICAL | All versions | No fix available |
About This Data
Vulnerability data for safe-eval is sourced from the Open Source Vulnerability (OSV) database, aggregating reports from GitHub Advisory Database, NIST NVD, and ecosystem-specific sources.
CVSS (Common Vulnerability Scoring System) scores reflect exploitability and impact. EPSS (Exploit Prediction Scoring System) scores indicate the probability of exploitation within the next 30 days. Vulnerabilities marked with are listed in the CISA Known Exploited Vulnerabilities (KEV) catalog.
Related npm (Node.js) Packages
Other packages in this ecosystem, ranked by shared vulnerabilities where available.
Check Your Dependencies
Scan your project to check if you're using a vulnerable version of safe-eval.