CVE-2026-44002

Info Disclosure in Vm2 Project Vm2 ≤ 3.11.0

Public PoCInfo Disclosure

Published

13 May 2026

Modified

17 June 2026

Patch / advisory

View advisory

CVSS Score v3.1 5.8

Click a component to see what it means

Raw vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:N/A:N

EPSS Score 0.0024 15th percentile

Risk Priority 45 floored blend · peak EPSS

Summary

CVE-2026-44002 is a medium-severity Generation of Error Message Containing Sensitive Information (CWE-209) vulnerability in Vm2 Project Vm2. Its CVSS base score is 5.8 (Medium).

Operationally, exploitation aligns with the MITRE ATT&CK technique Software (T1592.002); ranked at the 15th 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 SI-11 (Error Handling) — see the control section below for these in your framework.

OWASP Top 10 for Web (2025)

EU & UK References

🇪🇺 ENISA EUVD: EUVD-2026-30072

Vulnerability Data

vm2 is an open source vm/sandbox for Node.js. Prior to 3.11.0, vm2's CallSite wrapper class (intended as a safe wrapper for V8's native CallSite) blocks getThis() and getFunction() to prevent host object leakage, but allows getFileName() to return unsanitized host…

absolute paths. Any sandboxed code can extract the full directory structure, library paths, and framework versions of the host server. This vulnerability is fixed in 3.11.0.

CWE(s): CWE-209

Related Threats

MITRE ATT&CK Enterprise Techniques

T1592.002 Software Reconnaissance

Adversaries may gather information about the victim's host software that can be used during targeting.

attack.mitre.org →

T1082 System Information Discovery Discovery

An adversary may attempt to get detailed information about the operating system and hardware, including version, patches, hotfixes, service packs, and architecture.

attack.mitre.org →

T1592 Gather Victim Host Information Reconnaissance

Adversaries may gather information about the victim's hosts that can be used during targeting.

attack.mitre.org →

T1595 Active Scanning Reconnaissance

Adversaries may execute active reconnaissance scans to gather information that can be used during targeting.

attack.mitre.org →

Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2026-44003Same product: Vm2 Project Vm2

CVE-2026-44008Same product: Vm2 Project Vm2

CVE-2023-37903Same product: Vm2 Project Vm2

CVE-2026-44001Same product: Vm2 Project Vm2

CVE-2026-24781Same product: Vm2 Project Vm2

CVE-2026-44006Same product: Vm2 Project Vm2

CVE-2026-26332Same product: Vm2 Project Vm2

CVE-2026-24120Same product: Vm2 Project Vm2

CVE-2026-44009Same product: Vm2 Project Vm2

CVE-2026-43997Same product: Vm2 Project Vm2

Affected Assets

vm2 project

vm2

≤ 3.11.0

Mitigating Controls

Control response

Prevent

Stop it (NIST 800-53)

—

Detect

Catch it (NIST detect / respond)

—

Harden

Shrink the surface (DISA STIG)

—

Validate

Prove the fix (OWASP ASVS)

V16.5.1

Mitigating Controls (NIST 800-53 r5) AI

SI-11 Error Handling good match

si-11 directly requires error messages to avoid revealing exploitable information about the system or its data.

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.

PR.PS-06 mostly match

prevents

Secure SDLC practices directly require sanitized error handling to prevent sensitive data disclosure.

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.

A.8.28 Secure coding mostly match

prevents

Secure coding standards explicitly forbid exposing sensitive data in errors.

A.8.29 Security testing in development and acceptance mostly match

finds

Security testing can detect error messages that leak sensitive information.

A.8.15 Logging partial match

degrades

Logging policy can require suppression of sensitive data in error messages.

A.8.25 Secure development life cycle partial match

prevents

Secure SDLC mandates error-handling rules that avoid leaking sensitive information.