CVE-2023-29017

CRITICALNVD 10.010.0—
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 10.0 under NVD CVSS v3. EPSS exploit probability: 72.9%, top 1% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
Weaponized
10.0
EchelonGraph verdictPatch this weekExploitation is likely or a public exploit exists.
  • High exploitation likelihood — EPSS 63%
CISA-KEV: Not listedEPSS: 63%CVSS: 10.0Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

vm2 is a sandbox that can run untrusted code with whitelisted Node's built-in modules. Prior to version 3.9.15, vm2 was not properly handling host objects passed to Error.prepareStackTrace in case of unhandled async errors. A threat actor could bypass the sandbox protections to gain remote code execution rights on the host running the sandbox. This vulnerability was patched in the release of version 3.9.15 of vm2. There are no known workarounds.

CVSS v3
10.0
EG Score
10.0(medium)
EPSS
99.1%
KEV
Not listed

Published

April 6, 2023

Last Modified

November 21, 2024

Advisory Details (4)

Auto-updated Jul 11, 2026
🔬 Proof of concept available. Patch available. Sources: github_commit, github.
github Patch Available🟡 PoC Available

Sandbox Escape · Advisory · patriksimek/vm2 · GitHub

https://github.com/patriksimek/vm2/security/advisories/GHSA-7jxr-cg7f-gpgv
generic

[VM2 Sandbox Escape] Vulnerability in [email protected] · Issue #515 · patriksimek/vm2 · GitHub

https://github.com/patriksimek/vm2/issues/515
github_commit Patch Available

commit d534e5785f38 (patriksimek/vm2)

Patch available: patriksimek/vm2 3.9.15 (contains commit d534e5785f38)

https://github.com/patriksimek/vm2/commit/d534e5785f38307b70d3aac1945260a261a94d50
generic

vm2_3.9.14_exploit_1.js · GitHub

https://gist.github.com/seongil-wi/2a44e082001b959bfe304b62121fb76d

Affected Packages

(1 across 1 ecosystem)
npm(1)
PackageVulnerable rangeFixed inDependents
vm2—3.9.15—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 6× in last 7d / 30× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-11 08:25 UTCEPSS rescore
  2. 2026-07-11 08:25 UTCEPSS rescore
  3. 2026-07-09 19:08 UTCEPSS rescore
  4. 2026-07-09 19:08 UTCEPSS rescore
  5. 2026-07-08 15:13 UTCEPSS rescore
  6. 2026-07-05 02:28 UTCEPSS rescore
  7. 2026-07-02 16:59 UTCEPSS rescore
  8. 2026-07-01 15:04 UTCEPSS rescore
  9. 2026-06-28 04:54 UTCEPSS rescore
  10. 2026-06-28 00:34 UTCOSV refresh
  11. 2026-06-27 03:07 UTCEPSS rescore
  12. 2026-06-25 13:48 UTCEPSS rescore
  13. 2026-06-25 13:48 UTCEPSS rescore
  14. 2026-06-24 14:03 UTCEPSS rescore
  15. 2026-06-24 14:03 UTCEPSS rescore
  16. 2026-06-23 21:31 UTCEPSS rescore
  17. 2026-06-23 21:31 UTCEPSS rescore
  18. 2026-06-21 01:58 UTCEPSS rescore
  19. 2026-06-21 01:58 UTCEPSS rescore
  20. 2026-06-18 17:51 UTCEPSS rescore
  21. 2026-06-18 17:51 UTCEPSS rescore
  22. 2026-06-17 17:51 UTCEPSS rescore
  23. 2026-06-17 17:51 UTCEPSS rescore
  24. 2026-06-16 17:51 UTCEPSS rescore
  25. 2026-06-16 17:51 UTCEPSS rescore
Show 32 more
  1. 2026-06-15 17:47 UTCEPSS rescore
  2. 2026-06-14 23:16 UTCEPSS rescore
  3. 2026-06-13 22:59 UTCEPSS rescore
  4. 2026-06-13 22:59 UTCEPSS rescore
  5. 2026-06-12 23:10 UTCEPSS rescore
  6. 2026-06-11 13:59 UTCEPSS rescore
  7. 2026-06-10 22:17 UTCEPSS rescore
  8. 2026-06-10 13:21 UTCEPSS rescore
  9. 2026-06-10 13:21 UTCEPSS rescore
  10. 2026-06-10 11:17 UTCOSV refresh
  11. 2026-06-07 15:23 UTCEPSS rescore
  12. 2026-06-07 15:23 UTCEPSS rescore
  13. 2026-06-06 13:46 UTCEPSS rescore
  14. 2026-06-06 13:46 UTCEPSS rescore
  15. 2026-06-05 22:46 UTCEPSS rescore
  16. 2026-06-05 22:46 UTCEPSS rescore
  17. 2026-06-05 06:09 UTCEPSS rescore
  18. 2026-06-05 06:09 UTCEPSS rescore
  19. 2026-06-04 13:11 UTCEPSS rescore
  20. 2026-06-04 13:11 UTCEPSS rescore
  21. 2026-06-02 20:12 UTCEPSS rescore
  22. 2026-06-02 20:12 UTCEPSS rescore
  23. 2026-06-02 20:12 UTCEPSS rescore
  24. 2026-06-01 13:51 UTCEPSS rescore
  25. 2026-05-31 00:15 UTCEPSS rescore
  26. 2026-05-31 00:15 UTCEPSS rescore
  27. 2026-05-29 13:43 UTCEPSS rescore
  28. 2026-05-28 13:43 UTCEPSS rescore
  29. 2026-05-28 13:43 UTCEPSS rescore
  30. 2026-05-27 13:39 UTCEPSS rescore
  31. 2026-05-27 13:39 UTCEPSS rescore
  32. 2026-05-25 03:37 UTCEG score recompute

Publicly available exploits

(1 reference)

Working exploit code is in the public domain (1 GitHub PoC). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • GitHub PoCtimb-machine-mirrors/seongil-wi-CVE-2023-29017
    First seen Apr 7, 2023

    Clone from gist

    Open source ↗

Frequently asked(5)

What is CVE-2023-29017?
CVE-2023-29017 is a critical vulnerability published on April 6, 2023. vm2 is a sandbox that can run untrusted code with whitelisted Node's built-in modules. Prior to version 3.9.15, vm2 was not properly handling host objects passed to Error.prepareStackTrace in case of unhandled async errors. A threat actor could bypass the sandbox protections to gain remote code…
When was CVE-2023-29017 disclosed?
CVE-2023-29017 was first published in the National Vulnerability Database on April 6, 2023, with the most recent update on November 21, 2024. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2023-29017 actively exploited?
CVE-2023-29017 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 99.1% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2023-29017?
CVE-2023-29017 has a CVSS v3 base score of 10.0 (NVD).
How do I remediate CVE-2023-29017?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2023-29017, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2023-29017

Explore →

Is Your Infrastructure Affected by CVE-2023-29017?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs