CVE-2026-92947

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-10-05. 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-81596 (ENISA EUVD) · GHSA-fcqc-726x-5wfc (GitHub Security Advisories) · GHSA-x5qg-8pq6-39h6 (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.5%CVSS: 10.0Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

vm2 before 3.11.7 exposes Node's shared Buffer pool to sandboxed code, allowing disclosure of host memory used by Buffer.from, Buffer.concat, and related allocations. Sandboxed code can read and write to host-realm buffers by acquiring ArrayBuffers from small allocations, leading to sensitive data exposure and potential denial-of-service.

CVSS
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.5%
EPSS %ILE
42nd
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.5% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-11). 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

September 17, 2026

Last Modified

September 17, 2026

Advisory Details (2)

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

Sandboxed code can read and write host-realm memory via Node's shared Buffer pool · Advisory · patriksimek/vm2 · GitHub

https://github.com/patriksimek/vm2/security/advisories/GHSA-fcqc-726x-5wfc
Web page

vm2 before 3.11.7 Memory Disclosure via Buffer Pool | Advisories | VulnCheck

https://www.vulncheck.com/advisories/vm2-before-3.11.7-memory-disclosure-via-buffer-pool

Patch Availability(7)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatrhdh/rhdh-hub-rhel9:17931178132026-10-28redhat
redhatansible-automation-platform/bootc-automation-portal-rhel9:17918656602026-10-13redhat
redhatansible-automation-platform/automation-portal:17912953792026-10-12redhat
redhatansible-automation-platform/automation-portal:17912937802026-10-12redhat
redhatrhdh/rhdh-hub-rhel9:17913114952026-10-08redhat
redhatrhdh/red-hat-developer-hub-backstage-plugin-orchestrator-backend:17912512822026-10-06redhat
npmvm2 @ 3.11.7 (fixes <= 3.11.6)—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.7: fixed in 3.11.7
—

Weakness Classification(3)

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

Data Freshness Timeline

(refreshed 20× in last 7d / 71× 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 → 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 294 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 194 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2026-92947?
CVE-2026-92947 is a critical-severity vulnerability; its CVE record was published on September 17, 2026. vm2 before 3.11.7 exposes Node's shared Buffer pool to sandboxed code, allowing disclosure of host memory used by Buffer.from, Buffer.concat, and related allocations. Sandboxed code can read and write to host-realm buffers by acquiring ArrayBuffers from small allocations, leading to sensitive data…
When was CVE-2026-92947 made public?
CVE-2026-92947 was made public on August 24, 2026: that is the date its CVE record's CNA, VulnCheck, gives for when the vulnerability was made public. The CVE record itself was published on September 17, 2026. EchelonGraph's copy of the record carries a last-modified date of September 17, 2026; the record at its source may have been updated since.
Is CVE-2026-92947 actively exploited?
CVE-2026-92947 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (42nd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-92947?
CVE-2026-92947 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-92947?
A fix for CVE-2026-92947 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-92947 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-92947

Explore →

Is Your Infrastructure Affected by CVE-2026-92947?

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