vm2 is an open source vm/sandbox for Node.js. In 3.10.5, NodeVM's require.root path restriction can be bypassed using filesystem symlinks, allowing sandboxed code to load modules from outside the allowed root directory in host context. Because path validation uses path.resolve() (which does not dereference symlinks) but module loading uses Node's native require() (which does), an attacker can load arbitrary host-realm modules and achieve remote code execution. This vulnerability is fixed in 3.11.0.
Security readout for executives and security teams
Plain-English summary
CVE-2026-43998 lets sandboxed JavaScript escape an intended file-root boundary in vm2 NodeVM 3.10.5. A symlink handling mismatch can allow code to load host-side modules outside the allowed root, creating a path to remote code execution. The cited fix is vm2 3.11.0.
Executive priority
Treat this as a high-priority dependency remediation where vm2 is used to isolate untrusted code. The business risk is sandbox failure leading to host-code execution. Prioritize internet-facing, multi-tenant, or customer-script execution services first.
Technical view
NodeVM validates require.root paths with path.resolve(), which does not dereference symlinks, while Node's native require() does. In vm2 3.10.5 this mismatch can bypass the root restriction and load host-realm modules. The issue is classified as CWE-59 with CVSS 8.5.
Likely exposure
Exposure is most likely in applications that run untrusted or tenant-controlled JavaScript through vm2 3.10.5 NodeVM with require.root restrictions. Common risk areas include plugin execution, code runners, automation, and SaaS customization. The source bundle only identifies vm2 3.10.5 as affected.
Exploitation context
The supplied sources describe a sandbox escape condition, not confirmed exploitation in the wild. KEV is false, and no cited source states active exploitation. CVSS indicates network reachability, low privileges, no user interaction, changed scope, high impact, and high attack complexity.
Researcher notes
The key issue is inconsistent symlink treatment between path validation and module loading. Focus validation on vm2 3.10.5 NodeVM require.root usage and trust boundaries. Do not assume broader version impact beyond the cited affected version without vendor confirmation.
Mitigation direction
Upgrade affected vm2 installations from 3.10.5 to 3.11.0.
Identify dependency paths that introduce vm2 3.10.5 transitively.
Avoid running untrusted JavaScript in affected NodeVM configurations until upgraded.
Check vendor advisories and Red Hat VEX data for environment-specific status.
Validation and detection
Review SBOMs and lockfiles for patriksimek/vm2 version 3.10.5.
Confirm production builds resolve vm2 to 3.11.0 or later.
Inventory code paths using NodeVM and require.root restrictions.
Review sandbox-host module boundaries for symlink-accessible paths.
Track Red Hat advisory status if consuming vm2 through Red Hat channels.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-59: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
The CVE wording references privilege impact, so privilege escalation and authorization behavior review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
2CVSS vectors
5Timeline events
2ADP providers
5Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: pocAutomatable: noTechnical Impact: total
CVSS vector scores
2 official scores
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-59 · source CWE mapping
Improper Link Resolution Before File Access ('Link Following')
Improper Link Resolution Before File Access ('Link Following') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.