CVE-2026-47140

CRITICALPre-NVD 10.010.0
EchelonGraph scoreMEDIUM confidence

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

Score 10.0 from GitHub Security Advisory (severity: CRITICAL) published 2026-05-29. A secondary CVSS source baseline 10.0; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Trending — 4 sources updated this weekElevated

Also known asEUVD-2026-36446 (ENISA EUVD) · GHSA-rp36-8xq3-r6c4 (GitHub Security Advisories)Source: ENISA EUVD

10.0EG
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: 1.0%CVSS: 10.0Exploit: 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, NodeVM blocks several dangerous Node.js builtins such as module, worker_threads, cluster, vm, repl, and inspector. However, the denylist misses process and inspector/promises. Both can be used from sandboxed code to reach host-side execution primitives. This allows sandboxed code to bypass the intended builtin restrictions and execute code in the host process. This issue has been patched in version 3.11.4.

CVSS v3
10.0
EG Score
10.0CRITICALmedium confidence
EG Risk
76
EG Risk 76/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)
Severity100% × 45%
Impact severity (EG Severity): CVSS 10.0 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, Track* at medium and Attend at high mission impact.
Exploitation public PoC (CISA Vulnrichment) · Automatable yes (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 at low or medium mission impact and sooner than that at high.
EPSS PROB
1.0%
EPSS %ILE
62nd
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 (10.0): severity, escalated by confirmed exploitation. This CVE's 10.0 is its impact severity (EG Severity), not escalated.

EG Severity
10.0 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
1.0% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-01). 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, Track* at medium and Attend at high mission impact.CISA BOD 26-04: 3 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low, Track* at medium and Attend at high mission impact.

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 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)3 days if the affected system is publicly exposed; 60 days if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable yes (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

October 26, 2026

Advisory Details (3)

Auto-updated Nov 2, 2026
🔬 Proof of concept available. Patch available. Sources: github_commit, github_release, github.
GitHub advisoryMentions a patch (unverified)🟡 PoC Available

NodeVM builtin denylist bypass via process and inspector/promises allows host code execution · Advisory · patriksimek/vm2 · GitHub

https://github.com/patriksimek/vm2/security/advisories/GHSA-rp36-8xq3-r6c4
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 a1ed47a98d1c (patriksimek/vm2)

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

https://github.com/patriksimek/vm2/commit/a1ed47a98d1cc36cb48c0d566d55889688e0b59b

Patch Availability(4)

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
npmvm2 @ 3.11.4 (fixes <= 3.11.3)—ghsa

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 24× in last 7d / 82× 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 333 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 233 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2026-47140?
CVE-2026-47140 is a critical-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, NodeVM blocks several dangerous Node.js builtins such as module, worker_threads, cluster, vm, repl, and inspector. However, the denylist misses process and inspector/promises. Both can be used from sandboxed code to reach…
When was the CVE record for CVE-2026-47140 published?
The CVE record for CVE-2026-47140 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 October 26, 2026; the record at its source may have been updated since.
Is CVE-2026-47140 actively exploited?
CVE-2026-47140 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1.0% probability of exploitation in the next 30 days (62nd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-47140?
CVE-2026-47140 has a CVSS base score of 10.0 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-47140?
A fix for CVE-2026-47140 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-47140 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-47140

Explore →

Is Your Infrastructure Affected by CVE-2026-47140?

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