CVE-2026-47135

HIGHPre-NVD 8.78.7—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.7 under the CNA's CVSS (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 82% 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
8.7EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 8.7Exploit: None knownExposed: 0

A fix is available — apply it.

vm2 is an open source vm/sandbox for Node.js. Prior to version 3.11.4, Symbol.for override in setup-sandbox.js only intercepts 2 of 9 dangerous Node.js cross-realm symbols. Combined with the bridge's set/defineProperty/deleteProperty traps having no isDangerousCrossRealmSymbol key check, sandbox code can obtain real cross-realm symbols, write them to host objects, and control host-side behavior — verified with a full util.promisify hijack chain. This issue has been patched in version 3.11.4.

CVSS v3
8.7
EG Score
8.7(medium)
EG Risk
39(Track)
EG Risk 39/100SSVC: Track

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
Severity87% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
18%
KEV
Not listed

Published

May 29, 2026

Last Modified

June 13, 2026

Advisory Details (3)

Auto-updated Jun 12, 2026
Patch available. Sources: github_commit, github_release, github.
github Patch Available

Sandbox escape via unblocked cross-realm Symbol.for keys + missing bridge write-trap symbol checks · Advisory · patriksimek/vm2 · GitHub

https://github.com/patriksimek/vm2/security/advisories/GHSA-m5q2-4fm3-vfqp
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 928aef51898b (patriksimek/vm2)

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

https://github.com/patriksimek/vm2/commit/928aef51898b5c52a05f05a40c4cfeb52e172878

Vendor Advisories for CVE-2026-47135(4)

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

Patch Availability(3)

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

Frequently asked(5)

What is CVE-2026-47135?
CVE-2026-47135 is a high vulnerability published on May 29, 2026. vm2 is an open source vm/sandbox for Node.js. Prior to version 3.11.4, Symbol.for override in setup-sandbox.js only intercepts 2 of 9 dangerous Node.js cross-realm symbols. Combined with the bridge's set/defineProperty/deleteProperty traps having no isDangerousCrossRealmSymbol key check, sandbox…
When was CVE-2026-47135 disclosed?
CVE-2026-47135 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-47135 actively exploited?
CVE-2026-47135 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 81.6% of all scored CVEs.
What is the CVSS score of CVE-2026-47135?
CVE-2026-47135 has a CVSS v4.0 base score of 8.7 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-47135?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-47135, 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-47135

Explore →

Is Your Infrastructure Affected by CVE-2026-47135?

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

Start Free Scan →Browse All CVEs