CVE-2026-24781

CRITICALPre-NVD 9.89.8
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

This critical-severity CVE scores 9.8 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 1.2% (67th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source
Trending — 3 sources updated this weekElevated
9.8EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 1.2%CVSS: 9.8Exploit: No code on recordExposed services: Not assessed

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.8CRITICALmedium confidence
EG Risk
75
EG Risk 75/100

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 (value × EchelonGraph’s weight)
Severity98% × 45%
The EG Score, 9.8 of 10.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low, Track* at medium and Attend at high mission impact.
Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
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
1.2%
EPSS %ILE
67th
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track 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). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)3 days if the affected system is publicly exposed; 60 days if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

May 4, 2026

Last Modified

July 15, 2026

Advisory Details (10)

Auto-updated Oct 10, 2026
Patch available. Sources: redhat, github_commit, github_release, github.
Red HatMentions a patch (unverified)
https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-24781.json
Red Hat

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
Red HatMentions a patch (unverified)

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
Red HatMentions a patch (unverified)
https://access.redhat.com/errata/RHSA-2026:36754
Red HatMentions a patch (unverified)
https://access.redhat.com/errata/RHSA-2026:26234
GitHub advisoryMentions a patch (unverified)

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 / EcosystemFix (by version range) / 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 rangeFix by version rangeDependents
vm2—
  • every version up to 3.11.0: fixed in 3.11.0
—

Weakness Classification(3)

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

Data Freshness Timeline

(refreshed 20× in last 7d / 38× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 99 of 272 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 1 repeat row among the latest 100 is merged into the row it repeats. The 173 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same product + same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-24781?
CVE-2026-24781 is a critical-severity vulnerability; its CVE record was 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 the CVE record for CVE-2026-24781 published?
The CVE record for CVE-2026-24781 was published on May 4, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of July 15, 2026; the record at its source may have been updated since.
Is CVE-2026-24781 actively exploited?
CVE-2026-24781 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1.2% probability of exploitation in the next 30 days (67th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-24781?
CVE-2026-24781 has a CVSS base score of 9.8 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-24781?
A fix for CVE-2026-24781 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-24781 are linked in the Vendor Advisories panel on this page.

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.

Book a Demo →Browse All CVEs