CVE-2026-47210

CRITICALPre-NVD 9.89.8—
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.8 under the CNA's CVSS (NVD's own analysis pending). EPSS exploit probability: 1.8%, top 23% 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: cna:github_m, epss
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: 2%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.4, a sandbox escape vulnerability in vm2 allows arbitrary code execution in the host process when untrusted code is executed with async support on runtimes exposing WebAssembly JSPI (WebAssembly.promising / WebAssembly.Suspending). In the tested configuration, a JSPI-backed Promise can reach Promise.prototype.finally() in a way that bypasses the expected Promise-species hardening and exposes a host-originated rejection object to attacker-controlled species logic, breaking the sandbox boundary. This issue has been patched in version 3.11.4.

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
2%
EPSS %ILE
77%
KEV
Not listed

Published

May 29, 2026

Last Modified

June 13, 2026

Advisory Details (3)

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

v3.11.4

Patch available: patriksimek/vm2 v3.11.4

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

commit 6915fa4d9bce (patriksimek/vm2)

Patch available: patriksimek/vm2 v3.11.4 (contains commit 6915fa4d9bce)

https://github.com/patriksimek/vm2/commit/6915fa4d9bcebd47b9a4f39a1adc1aa94ef6ffc6
github Patch Available🟡 PoC Available

vm2 sandbox escape via JSPI-backed Promise `.finally()` species bypass · Advisory · patriksimek/vm2 · GitHub

https://github.com/patriksimek/vm2/security/advisories/GHSA-6j2x-vhqr-qr7q

Vendor Advisories for CVE-2026-47210(2)

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
redhatrhdh/rhdh-hub-rhel9:17834481842026-07-08redhat

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.4—

Weakness Classification(1)

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

Data Freshness Timeline

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

Frequently asked(5)

What is CVE-2026-47210?
CVE-2026-47210 is a critical vulnerability published on May 29, 2026. vm2 is an open source vm/sandbox for Node.js. Prior to version 3.11.4, a sandbox escape vulnerability in vm2 allows arbitrary code execution in the host process when untrusted code is executed with async support on runtimes exposing WebAssembly JSPI (WebAssembly.promising / WebAssembly.Suspending).…
When was CVE-2026-47210 disclosed?
CVE-2026-47210 was first published in the National Vulnerability Database on May 29, 2026, with the most recent update on June 13, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-47210 actively exploited?
CVE-2026-47210 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 2% probability of exploitation in the next 30 days, which ranks it in the top 23.1% of all scored CVEs.
What is the CVSS score of CVE-2026-47210?
CVE-2026-47210 has a CVSS v4.0 base score of 9.8 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-47210?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-47210, 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-47210

Explore →

Is Your Infrastructure Affected by CVE-2026-47210?

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

Start Free Scan →Browse All CVEs