CVE-2026-47137

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.4%, top 70% 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
10.0
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%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, the fix for GHSA-8hg8-63c5-gwmx (CVE-2023-37903) introduced a check in nodevm.js line 263 that blocks the combination nesting: true + require: false. However, the check uses strict equality (options.require === false), which is trivially bypassed by omitting the require option entirely. When require is not specified, options.require is undefined, not false. The strict equality check fails, so the security guard is skipped. Immediately after (line 280), the destructuring default require: requireOpts = false assigns requireOpts = false, producing the exact configuration the patch was designed to prevent. This issue has been patched in version 3.11.4.

CVSS v3
10.0
EG Score
10.0(medium)
EG Risk
—
EPSS
30.7%
KEV
Not listed

Published

May 29, 2026

Last Modified

June 13, 2026

Advisory Details (5)

Auto-updated Jul 21, 2026
🔬 Proof of concept available. Patch available. Sources: github_commit, github_release, github.
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 Patch Available🟡 PoC Available

vm2 Sandbox Escape vulnerability · CVE-2023-37903 · GitHub Advisory Database · GitHub

https://github.com/advisories/GHSA-g644-9gfx-q4q4
github_commit Patch Available

commit 86ab819f202c (patriksimek/vm2)

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

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

commit 01a7552add34 (patriksimek/vm2)

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

https://github.com/patriksimek/vm2/commit/01a7552add345d5a6862623884e6b79a85bf0568
github Patch Available

GHSA-8hg8-63c5-gwmx patch bypass: nesting:true without explicit require still allows full RCE · Advisory · patriksimek/vm2 · GitHub

https://github.com/patriksimek/vm2/security/advisories/GHSA-m4wx-m65x-ghrr

Vendor Advisories for CVE-2026-47137(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 9× in last 7d / 49× 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.

  1. 2026-07-22 14:08 UTCEPSS rescore
  2. 2026-07-21 15:24 UTCEPSS rescore
  3. 2026-07-20 17:08 UTCEPSS rescore
  4. 2026-07-19 14:31 UTCEPSS rescore
  5. 2026-07-19 02:29 UTCEPSS rescore
  6. 2026-07-18 10:04 UTCEPSS rescore
  7. 2026-07-16 17:03 UTCEPSS rescore
  8. 2026-07-16 10:00 UTCVendor advisory
  9. 2026-07-16 01:58 UTCVendor advisory
  10. 2026-07-15 16:57 UTCEPSS rescore
  11. 2026-07-15 02:00 UTCEPSS rescore
  12. 2026-07-14 18:29 UTCVendor advisory
  13. 2026-07-14 14:06 UTCVendor advisory
  14. 2026-07-13 22:30 UTCEPSS rescore
  15. 2026-07-13 06:13 UTCEPSS rescore
  16. 2026-07-12 05:46 UTCEPSS rescore
  17. 2026-07-12 02:49 UTCVendor advisory
  18. 2026-07-11 22:24 UTCVendor advisory
  19. 2026-07-11 17:31 UTCVendor advisory
  20. 2026-07-11 08:27 UTCEPSS rescore
  21. 2026-07-09 19:10 UTCEPSS rescore
  22. 2026-07-08 22:42 UTCVendor advisory
  23. 2026-07-08 17:21 UTCVendor advisory
  24. 2026-07-08 15:16 UTCEPSS rescore
  25. 2026-07-07 13:46 UTCEPSS rescore
Show 40 more
  1. 2026-07-06 16:27 UTCEPSS rescore
  2. 2026-07-06 02:23 UTCEPSS rescore
  3. 2026-07-04 06:31 UTCEPSS rescore
  4. 2026-07-02 23:33 UTCVendor advisory
  5. 2026-07-02 19:14 UTCVendor advisory
  6. 2026-07-02 12:52 UTCVendor advisory
  7. 2026-07-02 08:33 UTCVendor advisory
  8. 2026-07-02 04:12 UTCVendor advisory
  9. 2026-07-01 18:49 UTCVendor advisory
  10. 2026-07-01 15:07 UTCEPSS rescore
  11. 2026-07-01 13:05 UTCVendor advisory
  12. 2026-07-01 08:39 UTCVendor advisory
  13. 2026-07-01 01:31 UTCVendor advisory
  14. 2026-06-30 23:22 UTCEPSS rescore
  15. 2026-06-29 14:06 UTCEPSS rescore
  16. 2026-06-29 14:06 UTCEPSS rescore
  17. 2026-06-28 14:07 UTCEPSS rescore
  18. 2026-06-28 04:56 UTCEPSS rescore
  19. 2026-06-28 04:56 UTCEPSS rescore
  20. 2026-06-27 03:08 UTCEPSS rescore
  21. 2026-06-25 13:49 UTCEPSS rescore
  22. 2026-06-24 14:05 UTCEPSS rescore
  23. 2026-06-23 21:33 UTCEPSS rescore
  24. 2026-06-23 21:33 UTCEPSS rescore
  25. 2026-06-22 14:25 UTCEPSS rescore
  26. 2026-06-22 14:25 UTCEPSS rescore
  27. 2026-06-21 14:56 UTCEPSS rescore
  28. 2026-06-21 14:56 UTCEPSS rescore
  29. 2026-06-21 01:59 UTCEPSS rescore
  30. 2026-06-21 01:59 UTCEPSS rescore
  31. 2026-06-19 19:26 UTCEPSS rescore
  32. 2026-06-19 19:26 UTCEPSS rescore
  33. 2026-06-18 17:52 UTCEPSS rescore
  34. 2026-06-18 17:52 UTCEPSS rescore
  35. 2026-06-17 17:53 UTCEPSS rescore
  36. 2026-06-16 17:53 UTCEPSS rescore
  37. 2026-06-15 17:49 UTCEPSS rescore
  38. 2026-06-13 23:00 UTCEPSS rescore
  39. 2026-06-12 23:12 UTCEPSS rescore
  40. 2026-05-29 18:20 UTCEG score recompute

Frequently asked(5)

What is CVE-2026-47137?
CVE-2026-47137 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, the fix for GHSA-8hg8-63c5-gwmx (CVE-2023-37903) introduced a check in nodevm.js line 263 that blocks the combination nesting: true + require: false. However, the check uses strict equality (options.require === false), which is…
When was CVE-2026-47137 disclosed?
CVE-2026-47137 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-47137 actively exploited?
CVE-2026-47137 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 30.7% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-47137?
CVE-2026-47137 has a CVSS v4.0 base score of 10.0 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-47137?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-47137, 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-47137

Explore →

Is Your Infrastructure Affected by CVE-2026-47137?

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

Start Free Scan →Browse All CVEs