CVE-2026-92939
Raw vector
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:XCVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.
Summary
CVE-2026-92939 is a critical-severity Process Control (CWE-114) vulnerability. Its CVSS base score is 9.4 (Critical).
Operationally, exploitation aligns with the MITRE ATT&CK technique Terminal Services DLL (T1505.005); ranked at the 44th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.
The strongest mitigations our analysis identified map to CM-11 (User-installed Software) and CM-7 (Least Functionality) — see the control section below for these in your framework.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2026-81589
Vulnerability Data
vm2 3.11.3 through 3.11.6 exposes the host Node.js crypto module to a NodeVM sandbox when the crypto builtin is allowed. The module is presented via a recursive read-only proxy, but its callable exports still execute with host-process authority. Sandboxed JavaScript…
more
can therefore call crypto.setEngine() with a filesystem path to an attacker-supplied native library (for example, one bundled in an untrusted plugin package already written to disk); OpenSSL asks the operating-system dynamic loader to load the file, and the library's constructor executes native code in the host process before engine-symbol validation rejects it. Exploitation requires only the crypto builtin and does not require fs, process, module, child_process, worker_threads, vm, or inspector access, resulting in a sandbox escape and arbitrary native code execution. Fixed in 3.11.7.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
- 6 hardening rules · 4 OS baselines
—
Mitigating Controls (NIST 800-53 r5) AI
Policies and enforcement for user-installed software prevent introduction and execution of untrusted libraries or commands.
Least functionality directly restricts execution of commands or loading of libraries to only approved capabilities, stopping untrusted sources from being used.
Mobile code control explicitly defines and enforces acceptable sources and technologies for code/commands loaded at runtime.
Malicious code protection mechanisms block execution or loading of code from untrusted sources before it can run.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Assessing authenticity/integrity before acquisition reduces use of untrusted sources for commands/libraries.
Hardened configuration baselines can enforce trusted paths and execution policies.
Explicitly prevents execution of unauthorized software, directly blocking untrusted commands or libraries.
Secure SDLC practices can embed checks against dynamic loading from untrusted sources.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Restricting software installation prevents loading untrusted libraries or executing commands from unknown sources.
Secure development lifecycle practices include controls on external code and command execution paths.
Application security requirements can mandate validation of external inputs and libraries.
Secure architecture principles discourage reliance on untrusted external processes or libraries.
Secure coding standards explicitly forbid executing or loading code from untrusted sources.
Security testing can detect unsafe process or library loading but does not prevent it by itself.
Hardening callouts derived
Configuration rules from DISA STIG baselines that bear on weaknesses of the type cited by this CVE. Each rule is shown with the relationship its mapping actually records, against the CWE it was authored against. Derived via CVE→CWE over `controls_xwalks` (higher-evidence rows only; rows rated `none` are excluded).
Oracle Linux 8 (3 rules)
- V-248568 OL 8 system commands must be owned by root. prevents CWE-114
- V-248567 OL 8 system commands must have mode 755 or less permissive. prevents CWE-114
- V-248569 OL 8 system commands must be group-owned by root or a system account. prevents CWE-114
Windows 10 (1 rule)
- V-220828 The default autorun behavior must be configured to prevent autorun commands. prevents CWE-114
Windows Server 2016 (1 rule)
- V-224933 The default AutoRun behavior must be configured to prevent AutoRun commands. prevents CWE-114
Windows Server 2019 (1 rule)
- V-205805 Windows Server 2019 default AutoRun behavior must be configured to prevent AutoRun commands. prevents CWE-114