{"id":"CVE-2026-92958","title":"vm2 through 3.11.6 contains a builtin-module denylist bypass in NodeVM","summary":"vm2 through 3.11.6 contains a builtin-module denylist bypass in NodeVM. When the embedder uses the builtin wildcard together with negative entries (e.g. require: { builtin: ['*', '-fs', '-child_process'] }), negative entries are matched …","severity":"high","cvss":8.5,"cvssVector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:H/A:L","cwe":["CWE-269","CWE-1220"],"vendor":"patriksimek","product":"vm2","affected":["vm2 < 3.11.7"],"published":"2026-09-17","updated":"2026-09-18","sourceUpdated":"2026-09-18T20:17:31.243","source":"NVD","sourceUrl":"https://nvd.nist.gov/vuln/detail/CVE-2026-92958","references":[{"url":"https://github.com/patriksimek/vm2/security/advisories/GHSA-6rh5-qq4q-97xh","label":"disclosure@vulncheck.com"},{"url":"https://www.vulncheck.com/advisories/vm2-before-3.11.7-denylist-bypass-via-fs-promises","label":"disclosure@vulncheck.com"},{"url":"https://github.com/patriksimek/vm2/security/advisories/GHSA-6rh5-qq4q-97xh","label":"134c704f-9b21-4f2e-91b3-4a467353bcc0"},{"url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-92958.json"},{"url":"https://access.redhat.com/security/cve/CVE-2026-92958"},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2536039"},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-92958"},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-92958"}],"tags":["nvd","cve.org","exploit-available","csaf","vex","red-hat"],"exploitAvailable":true,"ssvc":{"exploitation":"poc","automatable":"no","technicalImpact":"partial","timestamp":"2026-09-18T19:35:41.669234Z"},"epss":0.00278,"epssPercentile":0.20493,"ingestedAt":"2026-09-17T14:19:30.991Z","slug":"CVE-2026-92958","body":"## Overview\n\nvm2 through 3.11.6 contains a builtin-module denylist bypass in NodeVM. When the embedder uses the builtin wildcard together with negative entries (e.g. require: { builtin: ['*', '-fs', '-child_process'] }), negative entries are matched by exact module name in lib/builtin.js, so -fs removes only the builtin named fs and does not remove builtin subpaths such as fs/promises. Sandboxed code can therefore call require('fs/promises') or require('node:fs/promises') and reach the promise-based filesystem API despite fs being denied; node: prefix handling is likewise inconsistent (a -node:fs/promises entry does not block require('fs/promises')). Host file creation and writing were confirmed via fsp.writeFile(), and other fs/promises operations (cp, mkdir, rename, rm, rmdir, truncate, read operations, etc.) are also reachable. This issue is fixed in vm2 3.11.7.\n\n## Remediation\n\nRefer to the linked advisories for vendor-supplied fixes and affected version ranges.\n\n## Vendor advisories\n\n- **Red Hat VEX** · Important · affected: Red Hat Developer Hub, Self-service automation portal 2 · no fix planned: Red Hat Developer Hub, Self-service automation portal 2 · updated 2026-09-17 · [vex](https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-92958.json)","depth":"midnight","depthScore":59,"depthScoreParts":{"impact":46.8,"likelihood":0.1,"exploitation":12,"ransomware":0},"changes":[{"seq":207474,"id":"CVE-2026-92958","ts":1789761068924,"field":"exploit_available","old":"false","new":"true"}]}