CVE-2026-44001Public exploitNetwork attack vector

Host process crash via uncaught Promise rejection

Published May 13, 2026 · Updated May 13, 2026

Uncaught Promise exception in vm2 before 3.11.0 allows remote attackers to crash the host Node.js process through sandboxed code. localPromise in lib/setup-sandbox.js wraps the native Promise constructor without catching executor exceptions, allowing a host-realm TypeError from Error.stack formatting to escape as an unhandled rejection. Any path that runs attacker-controlled sandbox code is sufficient; on Node.js 15 and later, default unhandled-rejection behavior terminates the host process without exposing or modifying data.

CVSS severity8.6
High
EPSS probability0.45%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Uncaught Promise exception in vm2 before 3.11.0 allows remote attackers to crash the host Node.js process through sandboxed code. localPromise in lib/setup-sandbox.js wraps the native Promise constructor without catching executor exceptions, allowing a host-realm TypeError from Error.stack formatting to escape as an unhandled rejection. Any path that runs attacker-controlled sandbox code is sufficient; on Node.js 15 and later, default unhandled-rejection behavior terminates the host process without exposing or modifying data.

The record

CVE
CVE-2026-44001
Published
May 13, 2026
Updated
May 13, 2026
Vendor
Patrik Simek
Product
vm2
Classifications
CWE-248, T1499.004
Attack vector
network
Privileges
unauthenticated

Timeline

How it unfolded

  1. May 13, 2026CVE publishedPublication date reported by the CVE source.
  2. May 13, 2026Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=< 3.11.0

What conditions does exploitation require?

Attack vectornetwork
Required privilegesunauthenticated

What is affected?

Patrik Simek · vm2version=< 3.11.0

Published CVSS scores

8.6GitHubCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:N/A:H

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectornetwork
Privilegesunauthenticated
Known exploitationUnconfirmed
Public exploitPublished

Weakness, pattern, technique

CWE-248Uncaught Exception
T1499.004Application or System Exploitation

Public exploit references

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo