vm2 vulnerable to Inspect Manipulation

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

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

EPSS

• CVE-2023-32313: 0.79% estimated exploitation activity in the next 30 days; percentile 56.32 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

In versions 3.9.17 and lower of vm2 it was possible to get a read-write reference to the node inspect method and edit options for console.log. Impact A threat actor can edit options for console.log. Patches This vulnerability was patched in the release of version 3.9.18 of vm2. Workarounds After creating a vm make the inspect method readonly with vm.readonly(inspect). References PoC - https://gist.github.com/arkark/c1c57eaf3e0a649af1a70c2b93b17550 For more information If you have any questions or comments about this advisory: - Open an issue in VM2 Thanks to @arkark (Takeshi Kaneko) of GMO Cybersecurity by Ierae, Inc. for disclosing this vulnerability.

Published by the source

17 May 2023, 03:49 UTC

Last modified by the source

10 Sep 2026, 03:50 UTC

Source last checked

26 Oct 2026, 12:27 UTC

1. Revision 2 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-p5gc-c584-jj6v

2. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-p5gc-c584-jj6v

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2023-32313

Advisory: vm2 vulnerable to Inspect Manipulation
IDs: CVE-2023-32313, GHSA-p5gc-c584-jj6v
Record: https://patchnext.com/advisories/cve-2023-32313 (revision 2, source checked 26 Oct 2026, 12:27 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 5.3)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: vm2 3.9.18. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm vm2: affected < 3.9.18; fixed in 3.9.18

## Suggested inspection (read-only)
- `npm ls vm2 --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on vm2.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-p5gc-c584-jj6v (OSV record GHSA-p5gc-c584-jj6v lists affected ranges: npm vm2 >=0 <3.9.18 (fixed))
- Verified: https://github.com/advisories/GHSA-p5gc-c584-jj6v (GitHub-reviewed advisory GHSA-p5gc-c584-jj6v lists affected ranges: npm vm2 >=0 <3.9.18)

Commands are suggestions: review each one before running it.