vm2 is a widely used Node.js sandbox; this flaw allows sandboxed code to access host memory, risking broad data exposure and service disruption across organizations.
CVE-2026-92947
vm2 sandbox exposes host Buffer pool, enabling cross-realm memory read/write
Is CVE-2026-92947 being exploited?
Not confirmed. CVE-2026-92947 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.43% probability of exploitation in the next 30 days.
How severe is CVE-2026-92947?
CVE-2026-92947 is rated Critical with a CVSS score of 10.0. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-92947?
Yes. A fix has been recorded for CVE-2026-92947. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-92947 affect?
CVE-2026-92947 affects vm2 < 3.11.7, Node.js applications using vm2 sandbox, Services executing untrusted JS via vm2. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-92947?
Upgrade vm2 to >=3.11.7, audit/block untrusted code, isolate affected services
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Sandboxed code can read/write host process memory via Buffer allocations, exposing secrets, enabling data theft, DoS, or further compromise.
Immediate action required
- affected< 3.11.7
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.