CVE-2026-47209

HIGHPre-NVD 8.68.6
EchelonGraph scoreMEDIUM confidence

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

This high-severity CVE scores 8.6 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.5% (41st percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source
Trending — 3 sources updated this weekElevated
8.6EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.5%CVSS: 8.6Exploit: No code on recordExposed 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, the BaseHandler.set trap in bridge.js (line 1231) ignores the receiver parameter and unconditionally writes to the host target object. Per the Proxy set trap specification, when receiver !== proxy (e.g., when a child object inherits from the proxy via Object.create), the property assignment should create an own property on the receiver, not on the proxy target. The current implementation always calls otherReflectSet(object, key, value) against the host target, causing all inherited property writes to leak through to the host object. This bug provides an alternative attack vector for writing dangerous cross-realm Symbol keys (e.g., nodejs.util.promisify.custom) to host objects, bypassing any future per-trap isDangerousCrossRealmSymbol guard on the direct set path. This issue has been patched in version 3.11.4.

CVSS v3
8.6
EG Score
8.6HIGHmedium confidence
EG Risk
70
EG Risk 70/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity86% × 45%
Impact severity (EG Severity): CVSS 8.6 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (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 at low or medium mission impact and sooner than that at high.
EPSS PROB
0.5%
EPSS %ILE
41st
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (8.6): severity, escalated by confirmed exploitation. This CVE's 8.6 is its impact severity (EG Severity), not escalated.

EG Severity
8.6 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source · CVSS v3.0 or v3.1
EG Likelihood
0.5% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-19). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Attend at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source: the SSVC and BOD 26-04 blocks below.

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

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (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; 60 days if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact partial (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 12, 2026

Advisory Details (3)

Auto-updated Jun 12, 2026
Patch available. Sources: github_commit, github_release, github.
GitHub advisoryMentions a patch (unverified)

Bridge Proxy set trap ignores receiver parameter, enabling host object property injection via prototype chain · Advisory · patriksimek/vm2 · GitHub

https://github.com/patriksimek/vm2/security/advisories/GHSA-c4cf-2hgv-2qv6
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 26d0318b5e65 (patriksimek/vm2)

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

https://github.com/patriksimek/vm2/commit/26d0318b5e6555be4b187ba05d6cf378ccecfe22

Patch Availability(2)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatansible-automation-platform/automation-portal:17858542262026-08-05redhat
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 10× in last 7d / 34× 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 205 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 105 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2026-47209?
CVE-2026-47209 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, the BaseHandler.set trap in bridge.js (line 1231) ignores the receiver parameter and unconditionally writes to the host target object. Per the Proxy set trap specification, when receiver !== proxy (e.g., when a child object…
When was the CVE record for CVE-2026-47209 published?
The CVE record for CVE-2026-47209 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 12, 2026; the record at its source may have been updated since.
Is CVE-2026-47209 actively exploited?
CVE-2026-47209 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (41st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-47209?
CVE-2026-47209 has a CVSS base score of 8.6 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-47209?
A fix for CVE-2026-47209 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-47209 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-47209

Explore →

Is Your Infrastructure Affected by CVE-2026-47209?

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