CVE-2026-47208

CRITICALPre-NVD 10.010.0—
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 10.0 under the CNA's CVSS (NVD's own analysis pending). EPSS exploit probability: 0.5%, top 60% 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
Trending — 3 sources updated this weekElevated
10.0
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 1%CVSS: 10.0Exploit: NoneExposed: 0

A fix is available — apply it.

vm2 is an open source vm/sandbox for Node.js. Prior to version 3.11.4, 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.4.

CVSS v3
10.0
EG Score
10.0(medium)
EPSS
40.0%
KEV
Not listed

Published

May 29, 2026

Last Modified

June 13, 2026

Advisory Details (3)

Auto-updated Jul 14, 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 a46265500966 (patriksimek/vm2)

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

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

Sandbox Breakout Using Promise Species · Advisory · patriksimek/vm2 · GitHub

https://github.com/patriksimek/vm2/security/advisories/GHSA-76w7-j9cq-rx2j

Vendor Advisories for CVE-2026-47208(3)

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:17827612442026-06-30redhat

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 19× in last 7d / 119× 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 219 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-47208?
CVE-2026-47208 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, 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.4.
When was CVE-2026-47208 disclosed?
CVE-2026-47208 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-47208 actively exploited?
CVE-2026-47208 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 40.0% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-47208?
CVE-2026-47208 has a CVSS v4.0 base score of 10.0 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-47208?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-47208, 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-47208

Explore →

Is Your Infrastructure Affected by CVE-2026-47208?

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

Start Free Scan →Browse All CVEs