# CVE-2026-92947: vm2 before 3.11.7 Memory Disclosure via Buffer Pool

> Sandboxed code in vm2 can access host memory via shared Buffer pools, leading to sensitive data exposure and potential denial-of-service.

- **Severity:** Critical 10.0 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:L/SC:H/SI:H/SA:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 17 Sep 2026
- **Updated:** 17 Sep 2026
- **Also known as:** CLEANSTART-2026-XK86217, ECHO-e5bb-1e90-121a, GHSA-fcqc-726x-5wfc, MINI-x46j-w389-mqmp, ROOT-APP-NPM-CVE-2026-92947

## What is CVE-2026-92947?

CVE-2026-92947 is a critical vulnerability in patriksimek vm2, published on 17 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2026-92947?

2 open source packages ship an affected version, including vm2.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `vm2` | npm | All versions | 3.11.7 |
| `vm2` | npm | All versions | 3.11.7 |

## How do I fix CVE-2026-92947?

Upgrade vm2 to 3.11.7 or later.

## Is CVE-2026-92947 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-92947 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-92947 and fix it if it is affected.

What it is: CVE-2026-92947 is a critical vulnerability in patriksimek vm2, published on 17 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-92947 exists.

Affected packages and fixed versions:
- vm2 (npm): affected all versions; fixed in 3.11.7
- vm2 (npm): affected all versions; fixed in 3.11.7

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-92947/ (Markdown: https://insights.sbomify.com/CVE-2026-92947/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-92947
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-92947
- OSV: https://osv.dev/vulnerability/CVE-2026-92947

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-92947/
Summaries are generated and may contain mistakes; the official description above is the record.