CVE-2026-47137
CRITICALDescription
vm2 is an open source vm/sandbox for Node.js. Prior to version 3.11.4, the fix for GHSA-8hg8-63c5-gwmx (CVE-2023-37903) introduced a check in nodevm.js line 263 that blocks the combination nesting: true + require: false. However, the check uses strict equality (options.require === false), which is trivially bypassed by omitting the require option entirely. When require is not specified, options.require is undefined, not false. The strict equality check fails, so the security guard is skipped. Immediately after (line 280), the destructuring default require: requireOpts = false assigns requireOpts = false, producing the exact configuration the patch was designed to prevent. This issue has been patched in version 3.11.4.
How to fix
TridentStack Control can deploy fixes like this automatically across your Windows, macOS, and Linux fleet. See how it works
Remediation is compiled from vendor and distribution security advisories. Always confirm against the linked source for your exact version and platform.
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
Low risk: more likely to be exploited than 31% of all known CVEs.
References
Related Vulnerabilities
Other CWE-913 vulnerabilities, ordered by exploit likelihood. View all
| CVE | Severity | CVSS | EPSS | Exploited | Fix |
|---|---|---|---|---|---|
| CVE-2025-68613 | Critical | 9.9 | 98% | KEV | Fix |
| CVE-2023-50386 | High | 8.8 | 84% | - | Fix |
| CVE-2023-43177 | Critical | 9.8 | 82% | - | Fix |
| CVE-2023-29017 | Critical | 10.0 | 63% | - | Fix |
| CVE-2022-36067 | Critical | 10.0 | 48% | - | Fix |
| CVE-2023-6184 | Medium | 5.0 | 47% | - | - |
Common questions
How do I fix CVE-2026-47137?
Published advisories record a fix for 8 affected products. The "How to fix" section on this page lists the fixed version and source advisory for each one, so apply the entry matching what you actually run.
Is CVE-2026-47137 being actively exploited?
Not that we know of. CVE-2026-47137 is not in the CISA Known Exploited Vulnerabilities catalog. Its EPSS score of 0.38% is the estimated probability that it will be exploited in the next 30 days. That is higher than 31% of all scored CVEs.
How severe is CVE-2026-47137?
CVE-2026-47137 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.
What does CVE-2026-47137 affect?
Published advisories record a fix for registry.redhat.io/ansible-automation (Red Hat / RHEL), registry.redhat.io/ansible-automation (Rocky), registry.redhat.io/rhdh/rhdh (Rocky), registry.redhat.io/rhdh/rhdh (Red Hat / RHEL), and 4 more. Only products with a sourced advisory are listed, so treat this as what we can cite rather than a complete inventory.
Embed a live status badge for CVE-2026-47137
Markdown
[](https://tridentstack.com/cve/CVE-2026-47137)HTML
<a href="https://tridentstack.com/cve/CVE-2026-47137"><img src="https://tridentstack.com/cve/badge/CVE-2026-47137.svg" alt="CVE-2026-47137"></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-06-12.