CVE-2026-47135

HIGHPre-NVD 8.78.7
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

This high-severity CVE scores 8.7 under the CNA's CVSS (NVD's own analysis pending). EPSS exploit probability: 0.4% (36th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from the CNA's CVSS
Sources: the CNA's CVSS, EPSS
8.7EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 8.7Exploit: None knownExposed services: Not assessed

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.7HIGHmedium confidence
EG Risk
39
EG Risk 39/100

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 (value × EchelonGraph’s weight)
Severity87% × 45%
The EG Score, 8.7 of 10.
Exploitation0.4% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.4%
EPSS %ILE
36th
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

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 advisoryMentions a patch (unverified)

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 / EcosystemFix (by version range) / 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 rangeFix by version rangeDependents
vm2—
  • every version up to 3.11.4: fixed in 3.11.4
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 11× in last 7d / 28× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 100 of 200 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 100 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same product + same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-47135?
CVE-2026-47135 is a high-severity vulnerability; its CVE record was 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 the CVE record for CVE-2026-47135 published?
The CVE record for CVE-2026-47135 was published on May 29, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of June 13, 2026; the record at its source may have been updated since.
Is CVE-2026-47135 actively exploited?
CVE-2026-47135 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (36th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-47135?
CVE-2026-47135 has a CVSS base score of 8.7 (the CNA's own assessment, by github_m; NVD's own analysis pending).
How do I remediate CVE-2026-47135?
A fix for CVE-2026-47135 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-47135 are linked in the Vendor Advisories panel on this page.

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.

Book a Demo →Browse All CVEs