CVE-2026-44006

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-07. 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
Elevated

Also known asEUVD-2026-30076 (ENISA EUVD) · GHSA-qcp4-v2jj-fjx8 (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: 0.8%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 3.11.0, It is possible to reach BaseHandler.getPrototypeOf, which can be used to get arbitrary prototypes. This vulnerability is fixed in 3.11.0.

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
0.8%
EPSS %ILE
57th
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
0.8% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-12). 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 13, 2026

Last Modified

October 26, 2026

Advisory Details (5)

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

Sandbox Escape · Advisory · patriksimek/vm2 · GitHub

https://github.com/patriksimek/vm2/security/advisories/GHSA-qcp4-v2jj-fjx8
Red Hat

2477200 – (CVE-2026-44006) CVE-2026-44006 vm2: vm2: Sandbox escape via arbitrary prototype access leading to arbitrary code execution

https://bugzilla.redhat.com/show_bug.cgi?id=2477200
Red HatMentions a patch (unverified)

CVE-2026-44006 - Red Hat Customer Portal

Affected: Red Hat Enterprise Linux 8 or OpenShift Container Platform 4, is affected by this vulnerability and a fix may be released to a

https://access.redhat.com/security/cve/CVE-2026-44006
Red HatMentions a patch (unverified)
https://access.redhat.com/errata/RHSA-2026:50850

Vendor Advisories for CVE-2026-44006(2)

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 / EcosystemFix (by version range) / PatchReleasedSource
redhatansible-automation-platform/automation-portal:17858542262026-08-05redhat
npmvm2 @ 3.11.0 (fixes <= 3.10.5)—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.0: fixed in 3.11.0
—

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 19× in last 7d / 74× 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 its CVE.org record (CNA or CISA ADP). 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). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

Showing the most recent 100 of 337 rows 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 237 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2026-44006?
CVE-2026-44006 is a critical-severity vulnerability; its CVE record was published on May 13, 2026. vm2 is an open source vm/sandbox for Node.js. Prior to 3.11.0, It is possible to reach BaseHandler.getPrototypeOf, which can be used to get arbitrary prototypes. This vulnerability is fixed in 3.11.0.
When was the CVE record for CVE-2026-44006 published?
The CVE record for CVE-2026-44006 was published on May 13, 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-44006 actively exploited?
CVE-2026-44006 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.8% probability of exploitation in the next 30 days (57th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-44006?
CVE-2026-44006 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-44006?
A fix for CVE-2026-44006 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-44006 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-44006

Explore →

Is Your Infrastructure Affected by CVE-2026-44006?

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