CVE-2026-43997
Vm2 code injection
- Published13 May 2026
Description
vm2 is an open source vm/sandbox for Node.js. Prior to 3.11.0, it is possible to obtain the host Object. There are various ways to use the host Object, to escape the sandbox, one example would be using HostObject.getOwnPropertySymbols to obtain Symbol(nodejs.util.inspect.custom). This vulnerability is fixed in 3.11.0.
CVSS 3.1 breakdown
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:HAffected products
Remediation
References
- https://access.redhat.com/errata/RHSA-2026:50850
- https://access.redhat.com/security/cve/CVE-2026-43997
- https://bugzilla.redhat.com/show_bug.cgi?id=2477203
- https://github.com/patriksimek/vm2/security/advisories/GHSA-47x8-96vw-5wg6
- https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-43997.json
Related CVEs
Recent high-severity vulnerabilities sharing a weakness type.
Frequently asked
Is CVE-2026-43997 being actively exploited?
CVE-2026-43997 is not in the CISA KEV catalog. A public exploit reference exists, so treat it as exploitable. Its EPSS exploit probability is 0.77%.
How severe is CVE-2026-43997?
CVE-2026-43997 has a CVSS 3.1 base score of 10.0, rated critical. EPSS estimates a 0.77% probability of exploitation.
Which products are affected by CVE-2026-43997?
Affected products include Vm2.
How do I fix CVE-2026-43997?
Upgrade affected software to a fixed version, for example Vm2 3.11.0 or later, then confirm no affected versions remain in your inventory.
How Secuno handles this
Secuno correlates vulnerabilities like CVE-2026-43997 against the real software inventory on every managed device, every day. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.
Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.