CVE-2026-92949: vm2 3.9.6 before 3.11.7 Sandbox Bypass via Accessor Descriptor

Published Sep 17, 2026
·
Updated

vm2 versions from 3.9.6 before 3.11.7 fail to properly restrict access to accessor properties on frozen objects, allowing sandboxed scripts to bypass vm.freeze() and vm.readonly() protections. Attackers can use Object.getOwnPropertyDescriptor() or lookupSetter() to extract and invoke host object setters directly, mutating properties the embedder explicitly marked read-only.

Affected Software

1 affected component
npm/vm2>3.9.6<3.11.7

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade vm2 to a version that resolves this vulnerability.

    Fixed in 3.11.7
  2. Compensating control

    Ensure sandboxed code cannot reach or mutate host object properties by reviewing and hardening any host-object APIs exposed to vm2, since accessor descriptor methods like Object.getOwnPropertyDescriptor() and __lookupSetter__ can be used to extract and invoke setters that were intended to be read-only.

Event History

Sep 17, 2026
CVE Published
via MITRE·01:46 PM
Data Sourced
via MITRE·01:46 PM
DescriptionSeverityWeakness

Frequently Asked Questions

1

Who is exposed to this issue?

Applications using npm/vm2 versions from 3.9.6 before 3.11.7 are exposed when they run untrusted or attacker-controlled scripts in a vm2 sandbox and provide those scripts access to frozen or read-only host objects with accessor properties.

2

What does an attacker need to exploit it?

An attacker needs the ability to execute a script inside the affected vm2 sandbox. The script can use Object.getOwnPropertyDescriptor() or __lookupSetter__() to obtain and directly invoke a host object's setter.

3

What is the security impact?

The attacker can mutate properties that the embedder explicitly attempted to protect with vm.freeze() or vm.readonly(). The provided vector indicates integrity impact without confidentiality or availability impact.

4

How can I determine whether my application is affected?

Check whether your application uses npm/vm2 in the affected version range and exposes host objects to sandboxed code through vm.freeze() or vm.readonly(). Review those objects for accessor properties, particularly setters, that sandboxed scripts could inspect.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203