CVE-2026-43998: CWE-59: Improper Link Resolution Before File Access ('Link Following') in patriksimek vm2
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.
AI Analysis
Technical Summary
The vulnerability in vm2 3.10.5 arises from improper link resolution before file access (CWE-59). NodeVM's require.root path restriction relies on path.resolve() for validation, which does not dereference symbolic links. However, Node's native require() function follows symlinks when loading modules. An attacker with low privileges who can execute code in a NodeVM with require restrictions and access to symlinked paths can bypass the root path restriction and load arbitrary host-realm modules, leading to remote code execution. The vulnerability is fixed in vm2 3.11.0. Red Hat's advisory confirms the issue and the fix in 3.11.0, scoring the vulnerability 8.5 (CVSS 3.1) with high impact on confidentiality, integrity, and availability.
Potential Impact
An attacker with low privileges able to run code in a NodeVM sandbox with require.root restrictions and access to filesystem symlinks can bypass path restrictions to load arbitrary modules from the host environment. This leads to remote code execution with the privileges of the host process. The vulnerability affects confidentiality, integrity, and availability of the host system. No known exploits in the wild have been reported as of the advisory date.
Mitigation Recommendations
A fix is available in vm2 version 3.11.0. Users should upgrade from version 3.10.5 to 3.11.0 or later to remediate this vulnerability. No alternative mitigations are specified in the vendor advisory. Patch status is confirmed by Red Hat and the official vm2 advisory.
CVE-2026-43998: CWE-59: Improper Link Resolution Before File Access ('Link Following') in patriksimek vm2
Description
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.
CVSS v3.1
Score 8.5high
Affected software
patriksimek
vm2
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The vulnerability in vm2 3.10.5 arises from improper link resolution before file access (CWE-59). NodeVM's require.root path restriction relies on path.resolve() for validation, which does not dereference symbolic links. However, Node's native require() function follows symlinks when loading modules. An attacker with low privileges who can execute code in a NodeVM with require restrictions and access to symlinked paths can bypass the root path restriction and load arbitrary host-realm modules, leading to remote code execution. The vulnerability is fixed in vm2 3.11.0. Red Hat's advisory confirms the issue and the fix in 3.11.0, scoring the vulnerability 8.5 (CVSS 3.1) with high impact on confidentiality, integrity, and availability.
Potential Impact
An attacker with low privileges able to run code in a NodeVM sandbox with require.root restrictions and access to filesystem symlinks can bypass path restrictions to load arbitrary modules from the host environment. This leads to remote code execution with the privileges of the host process. The vulnerability affects confidentiality, integrity, and availability of the host system. No known exploits in the wild have been reported as of the advisory date.
Mitigation Recommendations
A fix is available in vm2 version 3.11.0. Users should upgrade from version 3.10.5 to 3.11.0 or later to remediate this vulnerability. No alternative mitigations are specified in the vendor advisory. Patch status is confirmed by Red Hat and the official vm2 advisory.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-05-04T20:24:31.917Z
- Cvss Version
- 3.1
- State
- PUBLISHED
- Vendor Advisory Urls
- [{"url":"https://access.redhat.com/security/cve/CVE-2026-43998","vendor":"Red Hat"}]
Threat ID: 6a04ba1fcbff5d8610f48253
Added to database: 05/13/2026, 17:51:27 UTC
Last enriched: 08/06/2026, 13:00:27 UTC
Last updated: 09/13/2026, 10:01:31 UTC
Views: 70
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.