CVE-2026-93603
CRITICALDescription
vm2 through 3.12.0 (fixed in 3.12.1) does not correctly handle a nullish `this` receiver in the apply trap of its bridge (lib/bridge.js): when sandboxed code calls a host-provided non-strict (sloppy-mode) function without a receiver — e.g. `fn()`, a detached method, `fn.call()`, `fn.apply(undefined)`, `Reflect.apply(fn, undefined, [])`, or `fn.bind()()` — the undefined receiver is passed straight through to the host call, and V8 substitutes the host realm's global object for `this`. vm2 then wraps and returns that object to the sandbox, giving sandboxed script a live proxy of the host global. This allows a complete sandbox escape: untrusted script can reach `process` and execute arbitrary code/commands on the host (for example via `process.getBuiltinModule('child_process').execSync`). Exploitation requires that the embedding application expose at least one non-strict host function to the sandbox; strict-mode and ES module host functions are not affected.
How to fix
No published remediation has been found for this vulnerability's affected products yet.
Mitigation guidance may be in the linked vendor advisories in the References section below.
TridentStack Control tracks known vulnerabilities across your Windows, macOS, and Linux fleet and shows the fix as soon as one is published. See how it works
CVSS v3 Vector
Exploitability
Impact
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
Exploit Intelligence
EPSS data unavailable for this CVE.
References
Related Vulnerabilities
Other CWE-94 (Code Injection) vulnerabilities, ordered by exploit likelihood. View all
| CVE | Severity | CVSS | EPSS | Exploited | Fix |
|---|---|---|---|---|---|
| CVE-2017-9841 | Critical | 9.8 | 100% | KEV | Fix |
| CVE-2015-1635 | Critical | 9.8 | 100% | KEV | - |
| CVE-2022-22954 | Critical | 9.8 | 100% | KEV + Ransom | - |
| CVE-2025-49704 | High | 8.8 | 100% | KEV + Ransom | Fix |
| CVE-2025-3248 | Critical | 9.8 | 100% | KEV + Ransom | Fix |
| CVE-2021-22204 | Medium | 6.8 | 100% | KEV | Fix |
Common questions
How do I fix CVE-2026-93603?
No published fix for CVE-2026-93603 has been found yet. Check the linked vendor advisories for guidance as it becomes available.
How severe is CVE-2026-93603?
CVE-2026-93603 has a CVSS v3 base score of 10.0, rated critical. CVSS rates the technical impact if the vulnerability is exploited, not how likely that is, so weigh it alongside the exploit-prediction score when you decide what to patch first.
Embed a live status badge for CVE-2026-93603
Markdown
[](https://tridentstack.com/cve/CVE-2026-93603)HTML
<a href="https://tridentstack.com/cve/CVE-2026-93603"><img src="https://tridentstack.com/cve/badge/CVE-2026-93603.svg" alt="CVE-2026-93603"></a>Find and fix vulnerabilities across your fleet
TridentStack Control continuously scans your Windows, macOS, and Linux fleet for known vulnerabilities, prioritizes them by severity and active exploitation, and patches them automatically.
This product uses NVD data but is not endorsed or certified by the NVD. EPSS scores courtesy of FIRST.org (https://www.first.org/epss). Source: CISA KEV Catalog. Data as of 2026-09-18.