# vm2: External module allowlist uses a raw prefix test, so a prefix-sharing sibling package is treated as allowlisted Advisory record · `GHSA-7q3f-wx44-378m` - **Identifiers:** `GHSA-7q3f-wx44-378m` · `CVE-2026-92945` - **State:** Confirmed - **Severity:** CVSS 2.3 Low - **Critical:** No - **Weakness (CWE):** [CWE-22](https://cwe.mitre.org/data/definitions/22.html) · [CWE-863](https://cwe.mitre.org/data/definitions/863.html) - **Tags:** [Path traversal](https://agentprime.io/advisories/tag/path-traversal.md) · [Broken access control](https://agentprime.io/advisories/tag/access-control.md) - **Published:** 1 Oct 2026 - **Updated:** 1 Oct 2026 - **Reviewed by a person:** No Published by the GitHub Advisory Database at 1 Oct 2026, 15:26 UTC. agentprime has not analysed this yet, so whether it affects any app is not known. ## Affected packages - `vm2` (npm): affected `<3.11.7`; fixed in `3.11.7` ## Machine-written summary Summary written by Claude Haiku from the source advisory. Not reviewed by a person. > GHSA-7q3f-wx44-378m affects the npm package vm2 in versions before 3.11.7. An external module allowlist check uses a plain string prefix test, so a package whose name shares a prefix with an allowlisted package (for example foo2 alongside foo) can be treated as allowlisted. An attacker would need code running in NodeVM under such an allowlist with transitive loading disabled, plus an allowlisted package that performs a relative require to the sibling, and could then reach a package that was not allowlisted. The fix is in 3.11.7, so upgrade vm2 to that version. Written 31 Oct 2026. ## Not analysed yet We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check. ## Severity and exploitation - 2.3 Low, CVSS 4.0: `CVSS:4.0/AV:N/AC:H/AT:P/PR:L/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N`, from CNA (VulnCheck) - **CISA KEV:** Not listed. - **EPSS:** 0.0028, the 20th percentile, on 10 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days. ## Timeline - 31 Oct 2026, 13:34 UTC: First seen by agentprime - 31 Oct 2026, 13:34 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-7q3f-wx44-378m) ## Sources - [GitHub Advisory Database: GHSA-7q3f-wx44-378m](https://github.com/advisories/GHSA-7q3f-wx44-378m) - [OSV: GHSA-7q3f-wx44-378m](https://osv.dev/vulnerability/GHSA-7q3f-wx44-378m) - - - - - - Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code. ## Check whether this affects you A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet. - With the agentprime MCP server (), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: - In a browser: reads your lockfile in the browser, never uploading it. - Whether it touches your code, with file and line: the Claude Code plugin, - As JSON: , or `POST https://api.agentprime.io/v1/match` with your packages () --- The web page: . Everything for agents: .