CVE-2026-47683

HIGHPre-NVD 8.78.7
EchelonGraph scoreMEDIUM confidence

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

This high-severity CVE scores 8.7 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.5% (45th 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 — 4 sources updated this weekElevated

Also known asEUVD-2026-60461 (ENISA EUVD) · GHSA-gmc2-2x9w-cgh9 (GitHub Security Advisories)Source: ENISA EUVD

8.7EG
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.7Exploit: 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.6, the bufferAllocLimit enforcement in lib/setup-sandbox.js does not cover Buffer.concat(list, totalLength) or Buffer.from(arrayLike) with an attacker-controlled length, allowing sandbox code to perform large synchronous host external-memory allocations that bypass the configured cap and can exhaust the host process. This issue is fixed in version 3.11.6.

CVSS v3
8.7
EG Score
8.7HIGHmedium 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)
Severity87% × 45%
Impact severity (EG Severity): CVSS 8.7 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
45th
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.7): severity, escalated by confirmed exploitation. This CVE's 8.7 is its impact severity (EG Severity), not escalated.

EG Severity
8.7 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-31). 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

August 17, 2026

Last Modified

October 23, 2026

Advisory Details (3)

Auto-updated Aug 17, 2026
Patch available. Sources: github, github_commit, github_release.
GitHub release Patch Available

v3.11.6

Patch available: patriksimek/vm2 3.11.6

https://github.com/patriksimek/vm2/releases/tag/3.11.6
GitHub commit Patch Available

commit 3ffb315512e6 (patriksimek/vm2)

Patch available: patriksimek/vm2 3.11.6 (contains commit 3ffb315512e6)

https://github.com/patriksimek/vm2/commit/3ffb315512e634cf85c447375e85d6c83d00a4bd
GitHub advisoryMentions a patch (unverified)

bufferAllocLimit cap bypassed by Buffer.concat and Buffer.from arrayLike · Advisory · patriksimek/vm2 · GitHub

https://github.com/patriksimek/vm2/security/advisories/GHSA-gmc2-2x9w-cgh9

Patch Availability(6)

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

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 11× in last 7d / 55× 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 139 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 39 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2026-47683?
CVE-2026-47683 is a high-severity vulnerability; its CVE record was published on August 17, 2026. vm2 is an open source vm/sandbox for Node.js. Prior to 3.11.6, the bufferAllocLimit enforcement in lib/setup-sandbox.js does not cover Buffer.concat(list, totalLength) or Buffer.from(arrayLike) with an attacker-controlled length, allowing sandbox code to perform large synchronous host…
When was the CVE record for CVE-2026-47683 published?
The CVE record for CVE-2026-47683 was published on August 17, 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 23, 2026; the record at its source may have been updated since.
Is CVE-2026-47683 actively exploited?
CVE-2026-47683 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (45th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-47683?
CVE-2026-47683 has a CVSS base score of 8.7 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-47683?
A fix for CVE-2026-47683 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-47683 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-47683

Explore →

Is Your Infrastructure Affected by CVE-2026-47683?

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