CVE-2026-24118

CRITICALPre-NVD 9.89.8—
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.8 under NVD CVSS v3. EPSS exploit probability: 0.2%, top 61% 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
Elevated
9.8
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 1%CVSS: 9.8Exploit: NoneExposed: 0

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

vm2 is an open source vm/sandbox for Node.js. Prior to version 3.11.0, VM2 suffers from a sandbox breakout vulnerability. This allows attackers to write code which can escape from the VM2 sandbox and execute arbitrary commands on the host system. This issue has been patched in version 3.11.0.

CVSS v3
9.8
EG Score
9.8(medium)
EPSS
56.2%
KEV
Not listed

Published

May 4, 2026

Last Modified

July 15, 2026

Advisory Details (7)

Auto-updated Jul 16, 2026
🔬 Proof of concept available. Patch available. Sources: redhat, github_commit, github_release, github.
redhat
https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-24118.json
github Patch Available🟡 PoC Available

VM2 Sandbox Breakout Through __lookupGetter__ · Advisory · patriksimek/vm2 · GitHub

https://github.com/patriksimek/vm2/security/advisories/GHSA-grj5-jjm8-h35p
redhat

2466502 – (CVE-2026-24118) CVE-2026-24118 vm2: vm2: Arbitrary code execution due to sandbox breakout

https://bugzilla.redhat.com/show_bug.cgi?id=2466502
redhat Patch Available

cve-details

https://access.redhat.com/security/cve/CVE-2026-24118
github_release Patch Available

v3.11.0

Patch available: patriksimek/vm2 v3.11.0

https://github.com/patriksimek/vm2/releases/tag/v3.11.0
github_commit Patch Available

commit f9b700b1c7d9 (patriksimek/vm2)

Patch available: patriksimek/vm2 v3.11.0 (contains commit f9b700b1c7d9)

https://github.com/patriksimek/vm2/commit/f9b700b1c7d9ef2df416666cb24e0b659140cc74
github_commit Patch Available

commit 2b5f3e3a060d (patriksimek/vm2)

Patch available: patriksimek/vm2 v3.11.0 (contains commit 2b5f3e3a060d)

https://github.com/patriksimek/vm2/commit/2b5f3e3a060d9088f5e1cdd585d683d491f990a3

Affected Packages

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

Weakness Classification(3)

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

Data Freshness Timeline

(refreshed 12× in last 7d / 50× 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 192 total refreshes for this CVE.

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-24118?
CVE-2026-24118 is a critical vulnerability published on May 4, 2026. vm2 is an open source vm/sandbox for Node.js. Prior to version 3.11.0, VM2 suffers from a sandbox breakout vulnerability. This allows attackers to write code which can escape from the VM2 sandbox and execute arbitrary commands on the host system. This issue has been patched in version 3.11.0.
When was CVE-2026-24118 disclosed?
CVE-2026-24118 was first published in the National Vulnerability Database on May 4, 2026, with the most recent update on July 15, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-24118 actively exploited?
CVE-2026-24118 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 56.2% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-24118?
CVE-2026-24118 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2026-24118?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-24118, 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-2026-24118

Explore →

Is Your Infrastructure Affected by CVE-2026-24118?

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

Start Free Scan →Browse All CVEs