Sandbox Breakout in safe-eval
Affected versions of safe-eval are vulnerable to a sandbox escape. By accessing object constructors, un-sanitized user input can access the entire standard library and effectively break out of the sandbox.
Proof of Concept:
This code accesses the process object and calls .exit()
var safeEval = require('safe-eval');
safeEval("this.constructor.constructor('return process')().exit()");Recommendation
Update to version 0.4.0 or later
Affected software
Click a technology to see all vulnerabilities affecting it.
| Platform | Package | Vulnerable versions | Fixed in |
|---|---|---|---|
| npm package | safe-eval | <= 0.3.0 | no fix |
References
- CVSS vector
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H- Weakness (CWE)
CWE-610- Platform
- npm
- Package
safe-eval- Disclosed
- 18.07.2018
- Updated
- 11.10.2026 10:22
Sources and licenses
OSV / GitHub Advisory Database - GHSA-ww6v-677g-p656 - CC BY 4.0
Vulnerability history: safe-eval
All published vulnerabilities of this package (npm package), newest first. Shows whether this is a one-off slip or a package that needs watching.
- Total entries
- 6
- First → latest
- 07.2018 04.2023
- Without a fix
- 6
- Exploited in attacks
- 0
Severity breakdown
- Critical 5
- High 1
Disclosures per year
- 2018: 1
- 2019: 0
- 2020: 2
- 2021: 0
- 2022: 1
- 2023: 2
- 2024: 0
- 2025: 0
- 2026: 0
-
Sandbox Breakout in safe-eval this entry
Know which vulnerabilities affect your application
With the DockRay integration and software inventory enabled, DockRay checks reported component versions against known vulnerabilities and notifies you about confirmed matches. Coverage depends on the supported technology and available advisory data.