CVE-2026-24781

CRITICALPre-NVD 9.89.8
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.8 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 1.2%, top 35% 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, secondary
Elevated
9.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 9.8Exploit: Elevated riskExposed: 0

A fix is available — apply it.

vm2 is an open source vm/sandbox for Node.js. Prior to version 3.11.0, VM2 suffers from a sandbox breakout vulnerability through the inspect function. 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)
EG Risk
75(Attend)
EG Risk 75/100SSVC: Attend

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
Severity98% × 45%
Exploitation40% × 40%
Automatability100% × 15%
Action: Remediate soon — notable exploitation risk.
EPSS PROB
1%
EPSS %ILE
66%
KEV
Not listed

Published

May 4, 2026

Last Modified

July 15, 2026

Advisory Details (10)

Auto-updated Aug 29, 2026
🔬 Proof of concept available. Patch available. Sources: github_commit, github_release, github, redhat.
redhat

2466531 – (CVE-2026-24781) CVE-2026-24781 vm2: vm2: Arbitrary code execution via sandbox breakout through inspect function

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

CVE-2026-24781 - Red Hat Customer Portal

Affected: Red Hat Enterprise Linux 8 or OpenShift Container Platform 4, is affected by this vulnerability and a fix may be released to a

https://access.redhat.com/security/cve/CVE-2026-24781
github Patch Available🟡 PoC Available

Sandbox Breakout Through Inspect · Advisory · patriksimek/vm2 · GitHub

https://github.com/patriksimek/vm2/security/advisories/GHSA-v37h-5mfm-c47c
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 fd266d084e0a (patriksimek/vm2)

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

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

commit bdd3d15e57bc (patriksimek/vm2)

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

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

commit 8d30d93213c1 (patriksimek/vm2)

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

https://github.com/patriksimek/vm2/commit/8d30d93213c1898b3e035298b89a814970dd1189

Vendor Advisories for CVE-2026-24781(2)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(2)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatrhdh/rhdh-hub-rhel9:17834481842026-07-08redhat
redhatrhdh/rhdh-hub-rhel9:17811873422026-06-16redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
npm(1)
PackageVulnerable rangeFixed inDependents
vm23.11.0

Weakness Classification(3)

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

Data Freshness Timeline

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

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

Frequently asked(5)

What is CVE-2026-24781?
CVE-2026-24781 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 through the inspect function. 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…
When was CVE-2026-24781 disclosed?
CVE-2026-24781 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-24781 actively exploited?
CVE-2026-24781 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 34.4% of all scored CVEs.
What is the CVSS score of CVE-2026-24781?
CVE-2026-24781 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2026-24781?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-24781, 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-24781

Explore →

Is Your Infrastructure Affected by CVE-2026-24781?

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