CVE-2023-29017

CRITICALNVD 10.010.0—
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 10.0 under NVD CVSS v3. EPSS exploit probability: 63% (99th percentile of EPSS-scored CVEs). 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.0EG
EchelonGraph verdictPatch this weekExploitation is likely or a public exploit exists.
  • High exploitation likelihood — EPSS 63%
  • Public exploit code is available (ssvc poc, epss top5pct, epss high, public exploit)
CISA-KEV: Not listedEPSS PROB: 63%CVSS: 10.0Exploit: ssvc poc · epss top5pct · epss high · public exploitExposed services: Not assessed

A fix is available — apply it.

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.0CRITICALmedium confidence
EG Risk
86
EG Risk 86/100CISA SSVC

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity100% × 45%
Exploitation65% × 40%
Automatability100% × 15%
CISA SSVC: Track at low, Track* at medium and Attend at high mission impact.
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
63%
EPSS %ILE
99th
KEV
Not listed

CISA SSVCTrack at low, Track* at medium and Attend at high mission impact.

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

April 6, 2023

Last Modified

November 21, 2024

Advisory Details (4)

Auto-updated Oct 3, 2026
🔬 Proof of concept available. Patch available. Sources: github_commit, github.
githubMentions a patch (unverified)🟡 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 rangeFix by version rangeDependents
vm2—
  • every version up to 3.9.15: fixed in 3.9.15
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 4× in last 7d / 18× 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.

Showing the most recent 100 of 135 total refreshes for this CVE.

  1. 2026-10-09 20:05 UTCEPSS rescore
  2. 2026-10-07 23:45 UTCEPSS rescore
  3. 2026-10-06 15:15 UTCEPSS rescore
  4. 2026-10-03 14:23 UTCEPSS rescore
  5. 2026-10-02 16:23 UTCEPSS rescore
  6. 2026-10-01 19:47 UTCEPSS rescore
  7. 2026-09-30 16:21 UTCEG score recompute
  8. 2026-09-30 15:01 UTCEPSS rescore
  9. 2026-09-27 13:42 UTCEPSS rescore
  10. 2026-09-26 00:22 UTCEPSS rescore
  11. 2026-09-24 14:01 UTCEPSS rescore
  12. 2026-09-23 15:34 UTCOSV refresh
  13. 2026-09-23 13:45 UTCEPSS rescore
  14. 2026-09-22 14:45 UTCEPSS rescore
  15. 2026-09-16 14:05 UTCEPSS rescore
  16. 2026-09-13 16:44 UTCEPSS rescore
  17. 2026-09-12 14:58 UTCEPSS rescore
  18. 2026-09-11 09:34 UTCEPSS rescore
  19. 2026-09-08 21:57 UTCEPSS rescore
  20. 2026-09-06 13:45 UTCEPSS rescore
  21. 2026-09-05 15:25 UTCEPSS rescore
  22. 2026-09-04 13:58 UTCEPSS rescore
  23. 2026-09-04 10:16 UTCOSV refresh
  24. 2026-09-02 14:09 UTCEPSS rescore
  25. 2026-08-30 19:15 UTCEPSS rescore
Show 75 more
  1. 2026-08-30 01:19 UTCEPSS rescore
  2. 2026-08-28 21:38 UTCEPSS rescore
  3. 2026-08-27 14:23 UTCEPSS rescore
  4. 2026-08-26 14:43 UTCEPSS rescore
  5. 2026-08-25 13:46 UTCEPSS rescore
  6. 2026-08-24 14:14 UTCEPSS rescore
  7. 2026-08-21 23:46 UTCEPSS rescore
  8. 2026-08-20 22:53 UTCEPSS rescore
  9. 2026-08-19 17:02 UTCEPSS rescore
  10. 2026-08-18 13:46 UTCEPSS rescore
  11. 2026-08-17 20:59 UTCOSV refresh
  12. 2026-08-17 13:44 UTCEPSS rescore
  13. 2026-08-16 14:53 UTCEPSS rescore
  14. 2026-08-16 02:12 UTCEPSS rescore
  15. 2026-08-15 01:28 UTCEPSS rescore
  16. 2026-08-13 21:58 UTCEPSS rescore
  17. 2026-08-12 13:48 UTCEPSS rescore
  18. 2026-08-11 13:39 UTCEPSS rescore
  19. 2026-08-06 13:44 UTCEPSS rescore
  20. 2026-08-05 19:15 UTCEPSS rescore
  21. 2026-08-05 19:15 UTCEPSS rescore
  22. 2026-08-03 10:34 UTCEPSS rescore
  23. 2026-08-02 16:27 UTCOSV refresh
  24. 2026-08-02 02:25 UTCEPSS rescore
  25. 2026-08-02 02:24 UTCEPSS rescore
  26. 2026-07-30 16:26 UTCEPSS rescore
  27. 2026-07-30 16:26 UTCEPSS rescore
  28. 2026-07-30 01:28 UTCEPSS rescore
  29. 2026-07-30 01:28 UTCEPSS rescore
  30. 2026-07-28 15:34 UTCEPSS rescore
  31. 2026-07-28 15:34 UTCEPSS rescore
  32. 2026-07-26 14:52 UTCEPSS rescore
  33. 2026-07-26 14:52 UTCEPSS rescore
  34. 2026-07-25 14:16 UTCEPSS rescore
  35. 2026-07-24 14:15 UTCEPSS rescore
  36. 2026-07-23 14:16 UTCEPSS rescore
  37. 2026-07-23 14:16 UTCEPSS rescore
  38. 2026-07-23 02:21 UTCEG score recompute
  39. 2026-07-22 23:09 UTCEG score recompute
  40. 2026-07-22 14:06 UTCEPSS rescore
  41. 2026-07-22 14:06 UTCEPSS rescore
  42. 2026-07-21 15:23 UTCEPSS rescore
  43. 2026-07-20 17:06 UTCEPSS rescore
  44. 2026-07-16 17:01 UTCEPSS rescore
  45. 2026-07-16 17:01 UTCEPSS rescore
  46. 2026-07-16 00:19 UTCOSV refresh
  47. 2026-07-15 16:56 UTCEPSS rescore
  48. 2026-07-15 16:56 UTCEPSS rescore
  49. 2026-07-13 22:28 UTCEPSS rescore
  50. 2026-07-13 22:28 UTCEPSS rescore
  51. 2026-07-13 06:11 UTCEPSS rescore
  52. 2026-07-13 06:11 UTCEPSS rescore
  53. 2026-07-12 05:45 UTCEPSS rescore
  54. 2026-07-11 08:25 UTCEPSS rescore
  55. 2026-07-11 08:25 UTCEPSS rescore
  56. 2026-07-09 19:08 UTCEPSS rescore
  57. 2026-07-09 19:08 UTCEPSS rescore
  58. 2026-07-08 15:13 UTCEPSS rescore
  59. 2026-07-05 02:28 UTCEPSS rescore
  60. 2026-07-02 16:59 UTCEPSS rescore
  61. 2026-07-01 15:04 UTCEPSS rescore
  62. 2026-06-28 04:54 UTCEPSS rescore
  63. 2026-06-28 00:34 UTCOSV refresh
  64. 2026-06-27 03:07 UTCEPSS rescore
  65. 2026-06-25 13:48 UTCEPSS rescore
  66. 2026-06-25 13:48 UTCEPSS rescore
  67. 2026-06-24 14:03 UTCEPSS rescore
  68. 2026-06-24 14:03 UTCEPSS rescore
  69. 2026-06-23 21:31 UTCEPSS rescore
  70. 2026-06-23 21:31 UTCEPSS rescore
  71. 2026-06-21 01:58 UTCEPSS rescore
  72. 2026-06-21 01:58 UTCEPSS rescore
  73. 2026-06-18 17:51 UTCEPSS rescore
  74. 2026-06-18 17:51 UTCEPSS rescore
  75. 2026-06-17 17:51 UTCEPSS rescore

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 ↗

Related CVEs(same product + same CWE)

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 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. EchelonGraph's EG-KEV model classifies it as weaponized: a functional public exploit exists. FIRST EPSS estimates a 63% probability of exploitation in the next 30 days (99th percentile of EPSS-scored CVEs).
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?
A fix for CVE-2023-29017 is available: update to the fixed version the vendor names in its advisory.

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.

Book a Demo →Browse All CVEs