vm2: External module allowlist uses a raw prefix test, so a prefix-sharing sibling package is treated as allowlisted

Exploitation

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

CVSS

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

EPSS

• CVE-2026-92945: 0.28% estimated exploitation activity in the next 30 days; percentile 20.25 (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.

Summary isPathAllowedForModule decides whether a resolved path belongs to an allowlisted external module using a raw string prefix test. nodemodules/foo2 starts with nodemodules/foo, so a package whose name merely shares a prefix with an allowlisted one is treated as being inside it, and a relative require from the allowlisted package reaches it even with transitive loading disabled. Where it is lib/resolver-compat.js, lines 122 to 132, quoted from HEAD 7a1f5100b96f48d34e0fe104ab37c0acc5944f92: With mod.path of .../nodemodules/foo and a resolved path of .../nodemodules/foo2/index.js, startsWith is true and rem is 2/index.js, which contains no nodemodules segment, so the function returns true. The nodemodules test in rem is what stops a genuine transitive dependency from slipping through. It does not stop a sibling, because a sibling's remainder never contains that segment. Impact Code running in NodeVM under an external module allowlist with transitive: false can reach a package that…

Published by the source

1 Oct 2026, 15:26 UTC

Last modified by the source

1 Oct 2026, 15:45 UTC

Source last checked

26 Oct 2026, 13:06 UTC

1. Revision 3 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-7q3f-wx44-378m

2. Revision 2 · amended · 24 Oct 2026

   Amended from osv record GHSA-7q3f-wx44-378m

3. Revision 1 · created · 23 Oct 2026

   Published from ghsa record GHSA-7q3f-wx44-378m

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

# Patch Next advisory brief: CVE-2026-92945

Advisory: vm2: External module allowlist uses a raw prefix test, so a prefix-sharing sibling package is treated as allowlisted
IDs: CVE-2026-92945, GHSA-7q3f-wx44-378m
Record: https://patchnext.com/advisories/cve-2026-92945 (revision 3, source checked 26 Oct 2026, 13:06 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 4.2)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: vm2 3.11.7. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm vm2: affected <= 3.11.6; fixed in 3.11.7

## 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://github.com/advisories/GHSA-7q3f-wx44-378m (GitHub-reviewed advisory GHSA-7q3f-wx44-378m lists affected ranges: npm vm2 >=0 <=3.11.6)
- Verified: https://osv.dev/vulnerability/GHSA-7q3f-wx44-378m (OSV record GHSA-7q3f-wx44-378m lists affected ranges: npm vm2 >=0 <3.11.7 (fixed))

Commands are suggestions: review each one before running it.