Skip to content
Fencer Vulns
critical 10.0

CVE-2017-16088 json

Sandbox Breakout in safe-eval

published 2018-06-07 8 y ago modified 2026-06-17 4 mo ago also GHSA-ww6v-677g-p656 , EUVD-2018-0337

cvss
10.0
version 3.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
3.4%
EPSS 3.4% chance of exploitation in 30 days, percentile 89%
public exploits
0
none known

Summary

The safe-eval module describes itself as a safer version of eval. By accessing the object constructors, un-sanitized user input can access the entire standard library and effectively break out of the sandbox.

Patch / fix

Exploit prediction

3.44% chance of exploitation in the next 30 days, higher than 89% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
NVD 3.0 10.0 CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
NVD 2.0 10.0 AV:N/AC:L/Au:N/C:C/I:C/A:C
GitHub 3.0 10.0 CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H

Affected packages

ecosystem package affected fixed in
npm safe-eval
<=0.3.0
no fix listed

Affected products

  • HackerOne safe-eval node module

Classification

Weakness
  • CWE-610 Externally Controlled Reference to a Resource in Another Sphere

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.