CVE-2026-47209

HIGHPre-NVD 8.68.6—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.6 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 79% 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: epss, secondary
8.6EG
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.6Exploit: 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, 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.6(medium)
EG Risk
43(Track)
EG Risk 43/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
Severity86% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
21%
KEV
Not listed

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 Patch Available

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

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-47209?
CVE-2026-47209 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, 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 CVE-2026-47209 disclosed?
CVE-2026-47209 was first published in the National Vulnerability Database on May 29, 2026, with the most recent update on June 12, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-47209 actively exploited?
CVE-2026-47209 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 79.1% of all scored CVEs.
What is the CVSS score of CVE-2026-47209?
CVE-2026-47209 has a CVSS v3 base score of 8.6 (NVD).
How do I remediate CVE-2026-47209?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-47209, 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-47209

Explore →

Is Your Infrastructure Affected by CVE-2026-47209?

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

Start Free Scan →Browse All CVEs