cve.bz

CVE-2026-100723 patriksimek vm2

6.9 mediumEPSS 0.4%Fix available

Medium (6.9) in patriksimek vm2. EPSS 0.4% estimated probability of exploitation activity in the next 30 days. Fixed in vm2 3.12.2.

On this page
vm2 before 3.12.2 does not apply its Buffer backing-store ownership invariant (byteOffset === 0 and buffer.byteLength === length) to Buffers returned from host builtin modules. When an application explicitly exposes Node's zlib module through NodeVM's builtin allowlist (require: { builtin: ['zlib'] }), zlib.deflateSync can return a Buffer backed by Node's shared small-buffer pool whose .buffer is the entire pool. Untrusted guest code can construct a full-width view of that ArrayBuffer (Buffer.from(result.buffer, 0, result.buffer.byteLength)) to read and modify bytes belonging to unrelated host buffers, disclosing and corrupting host-realm memory across the sandbox boundary.

Severity

CVSS 4.0

6.9 medium
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:N/SC:H/SI:L/SA:N

CVSS 3.1

7.5 high
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:L/A:N
EPSS
0.4% (unchanged from 0.4% a week ago; 0.3% 30 days ago) estimated probability of exploitation activity in the next 30 days; 34th percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: PoC · Automatable: no · Technical impact: partial, assessed 2026-10-01. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-200 Exposure of Sensitive Information to an Unauthorized Actor
OWASP Top 10
A01:2025 Broken Access Control
Published
Modified
NVD analysis
Deferred: the NVD does not plan to analyze it
Record from
the NVD, synced

Fix and patched versions

  • vm2 (npm): fixed in 3.12.2

Ask an AI about this CVE

Show the promptExplain CVE-2026-100723 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-100723?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-100723?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-100723 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
patriksimek vm2before 3.12.2

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-489w-w794-jq94npmvm2<3.12.23.12.2

Red Hat

Red Hat rates this Important.

Red Hat's statement

This vulnerability is rated as an Important severity because untrusted guest code can break sandbox isolation, allowing the disclosure and modification of host memory space. Exploitation requires an explicit, non-default configuration where the application grants the guest environment access to Node's builtin zlib compression module. Red Hat products shipping this library do not expose the vulnerable feature in their active execution paths, which prevents exposure under default configurations.

Red Hat's mitigation

Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability.

ProductPackageStateAdvisory
Red Hat Developer Hub 1rhdh/rhdh-hub-rhel9Not affected
Self-service automation portal 2ansible-automation-platform/bootc-automation-portal-rhel9Not affected

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-100723.

Attack patterns (CAPEC)

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits. More on the page of CWE-200 (59).

References

Check your stackJSON