CVE-2026-47683

HIGHPre-NVD 8.78.7—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.7 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.5% (43rd percentile of EPSS-scored CVEs). 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
Trending — 3 sources updated this weekElevated
8.7EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.5%CVSS: 8.7Exploit: Elevated riskExposed 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/100CISA SSVC

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
Severity87% × 45%
Exploitation40% × 40%
Automatability100% × 15%
CISA SSVC: Track at low, Track* at medium and Attend at high mission impact.
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
43rd
KEV
Not listed

CISA SSVCTrack 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). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

August 17, 2026

Last Modified

September 9, 2026

Advisory Details (3)

Auto-updated Aug 17, 2026
🔬 Proof of concept available. 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 Patch Available🟡 PoC Available

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

Vendor Advisories for CVE-2026-47683(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 / EcosystemFix (by version range) / PatchReleasedSource
redhatansible-automation-platform/automation-portal:17902549632026-09-28redhat
redhatansible-automation-platform/automation-portal:17902564052026-09-28redhat

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 18× in last 7d / 54× 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.

  1. 2026-10-04 23:22 UTCEPSS rescore
  2. 2026-10-04 21:49 UTCVendor advisory
  3. 2026-10-04 06:42 UTCVendor advisory
  4. 2026-10-03 17:48 UTCEG score recompute
  5. 2026-10-03 17:48 UTCVendor advisory
  6. 2026-10-03 14:25 UTCEPSS rescore
  7. 2026-10-02 15:45 UTCVendor advisory
  8. 2026-10-02 01:34 UTCEG score recompute
  9. 2026-10-02 01:34 UTCVendor advisory
  10. 2026-10-01 19:50 UTCEPSS rescore
  11. 2026-10-01 12:07 UTCVendor advisory
  12. 2026-09-30 22:54 UTCEG score recompute
  13. 2026-09-30 22:54 UTCVendor advisory
  14. 2026-09-30 15:03 UTCEPSS rescore
  15. 2026-09-30 10:00 UTCEG score recompute
  16. 2026-09-30 10:00 UTCVendor advisory
  17. 2026-09-28 23:42 UTCEG score recompute
  18. 2026-09-28 13:51 UTCEPSS rescore
  19. 2026-09-27 21:40 UTCEG score recompute
  20. 2026-09-27 13:48 UTCEPSS rescore
  21. 2026-09-27 08:06 UTCEG score recompute
  22. 2026-09-26 15:59 UTCEPSS rescore
  23. 2026-09-26 00:27 UTCEPSS rescore
  24. 2026-09-24 16:14 UTCEG score recompute
  25. 2026-09-24 00:53 UTCEG score recompute
Show 65 more
  1. 2026-09-23 17:53 UTCEPSS rescore
  2. 2026-09-22 23:02 UTCEG score recompute
  3. 2026-09-21 21:11 UTCEG score recompute
  4. 2026-09-21 08:16 UTCEG score recompute
  5. 2026-09-20 20:16 UTCEPSS rescore
  6. 2026-09-19 16:59 UTCEG score recompute
  7. 2026-09-19 04:03 UTCEG score recompute
  8. 2026-09-18 19:28 UTCEPSS rescore
  9. 2026-09-18 02:09 UTCEG score recompute
  10. 2026-09-16 23:42 UTCEG score recompute
  11. 2026-09-16 14:08 UTCEPSS rescore
  12. 2026-09-16 10:46 UTCEG score recompute
  13. 2026-09-16 05:15 UTCEPSS rescore
  14. 2026-09-15 08:47 UTCEG score recompute
  15. 2026-09-13 17:22 UTCEG score recompute
  16. 2026-09-13 16:47 UTCEPSS rescore
  17. 2026-09-12 15:32 UTCEG score recompute
  18. 2026-09-12 02:37 UTCEG score recompute
  19. 2026-09-11 14:53 UTCEPSS rescore
  20. 2026-09-11 13:38 UTCEG score recompute
  21. 2026-09-10 10:23 UTCEG score recompute
  22. 2026-09-10 09:34 UTCEPSS rescore
  23. 2026-09-09 03:39 UTCEG score recompute
  24. 2026-09-08 22:00 UTCEPSS rescore
  25. 2026-09-07 16:11 UTCEG score recompute
  26. 2026-09-07 16:01 UTCEPSS rescore
  27. 2026-09-07 01:38 UTCEG score recompute
  28. 2026-09-06 13:47 UTCEPSS rescore
  29. 2026-09-05 23:45 UTCEG score recompute
  30. 2026-09-04 21:54 UTCEG score recompute
  31. 2026-09-04 08:04 UTCEG score recompute
  32. 2026-09-04 05:06 UTCEPSS rescore
  33. 2026-09-02 17:08 UTCEG score recompute
  34. 2026-09-02 14:12 UTCEPSS rescore
  35. 2026-09-02 01:47 UTCEG score recompute
  36. 2026-09-01 13:54 UTCEPSS rescore
  37. 2026-09-01 12:10 UTCEG score recompute
  38. 2026-08-30 21:19 UTCEG score recompute
  39. 2026-08-30 19:17 UTCEPSS rescore
  40. 2026-08-30 08:23 UTCEG score recompute
  41. 2026-08-30 01:22 UTCEPSS rescore
  42. 2026-08-29 05:31 UTCEG score recompute
  43. 2026-08-28 21:41 UTCEPSS rescore
  44. 2026-08-27 20:49 UTCEG score recompute
  45. 2026-08-27 14:25 UTCEPSS rescore
  46. 2026-08-26 18:59 UTCEG score recompute
  47. 2026-08-26 14:46 UTCEPSS rescore
  48. 2026-08-25 17:06 UTCEG score recompute
  49. 2026-08-25 13:49 UTCEPSS rescore
  50. 2026-08-24 14:58 UTCEG score recompute
  51. 2026-08-23 13:06 UTCEG score recompute
  52. 2026-08-23 00:19 UTCEPSS rescore
  53. 2026-08-22 11:12 UTCEG score recompute
  54. 2026-08-21 23:49 UTCEPSS rescore
  55. 2026-08-21 09:22 UTCEG score recompute
  56. 2026-08-20 22:55 UTCEPSS rescore
  57. 2026-08-19 18:36 UTCEG score recompute
  58. 2026-08-19 17:04 UTCEPSS rescore
  59. 2026-08-18 16:46 UTCEG score recompute
  60. 2026-08-18 15:45 UTCEG score recompute
  61. 2026-08-18 13:48 UTCEPSS rescore
  62. 2026-08-17 21:32 UTCEG score recompute
  63. 2026-08-17 21:05 UTCEG score recompute▲ 8.70
  64. 2026-08-17 21:04 UTCMITRE cvelistV5CVSS v3 → 8.7 · CVSS v4 → 8.7
  65. 2026-08-17 17:54 UTCEG score recompute

Related CVEs(same product + same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-47683?
CVE-2026-47683 is a high vulnerability 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 CVE-2026-47683 disclosed?
CVE-2026-47683 was first published on August 17, 2026, with the most recent update on September 9, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
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 (43rd 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.

Book a Demo →Browse All CVEs