CVE-2026-45411

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: 0.6%, top 55% 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 3.11.3, it is possible to catch a host exception using the yield* expression inside an async generator. When the generator is closed using the return function, the value is awaited on and exceptions thrown in the then call will be caught by the runtime and passed to the yield* iterator as the next value. This allows attackers to write code which can escape from the VM2 sandbox and execute arbitrary commands on the host system. This vulnerability is fixed in 3.11.3.

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
45%
KEV
Not listed

Published

May 13, 2026

Last Modified

August 6, 2026

Advisory Details (5)

Auto-updated Aug 27, 2026
🔬 Proof of concept available. Patch available. Sources: github, redhat.
redhat Patch Available
https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-45411.json
github Patch Available🟡 PoC Available

Sandbox Breakout Using Async Generator · Advisory · patriksimek/vm2 · GitHub

https://github.com/patriksimek/vm2/security/advisories/GHSA-248r-7h7q-cr24
redhat

2477210 – (CVE-2026-45411) CVE-2026-45411 vm2: vm2: Arbitrary Code Execution due to sandbox escape vulnerability

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

CVE-2026-45411 - 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-45411
redhat Patch Available
https://access.redhat.com/errata/RHSA-2026:50850

Vendor Advisories for CVE-2026-45411(1)

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

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatansible-automation-platform/automation-portal:17858542262026-08-05redhat

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
vm2—3.11.3—

Weakness Classification(2)

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

Data Freshness Timeline

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

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

Frequently asked(5)

What is CVE-2026-45411?
CVE-2026-45411 is a critical vulnerability published on May 13, 2026. vm2 is an open source vm/sandbox for Node.js. Prior to 3.11.3, it is possible to catch a host exception using the yield expression inside an async generator. When the generator is closed using the return function, the value is awaited on and exceptions thrown in the then call will be caught by the…
When was CVE-2026-45411 disclosed?
CVE-2026-45411 was first published in the National Vulnerability Database on May 13, 2026, with the most recent update on August 6, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-45411 actively exploited?
CVE-2026-45411 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 55.2% of all scored CVEs.
What is the CVSS score of CVE-2026-45411?
CVE-2026-45411 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2026-45411?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-45411, 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-45411

Explore →

Is Your Infrastructure Affected by CVE-2026-45411?

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

Start Free Scan →Browse All CVEs