CVE-2026-112950Vitest: Windows backslash traversal bypasses the @vitest/mocker redirect allowlist fix
Updated under an hour ago ()
Does this affect you?
It affects vitest-dev vitest and 1 other product. Add what you run to find out whether that includes you.
No exploitation reported and no EPSS estimate yet.
Do this next
Free account, 1 product
Vitest is a Vite-native testing framework for JavaScript and TypeScript projects. From 4.1.11 until 4.1.12 and 5.0.3, isFileLoadingAllowed and the filesystem read interpret backslashes differently on Windows in packages/mocker/src/node/interceptorPlugin.ts. When a client can reach the Vite dev server on Windows and register a redirect mock containing backslash traversal, POSIX joining preserves a Windows backslash traversal that the later filesystem read interprets as a path separator, so the client can read a file outside server.fs.allow that the Vitest process can access. This issue is fixed in versions 4.1.12 and 5.0.3.
- CVSS
- 5.9 MEDIUM (v3.1, CNA)CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
- Weakness (CWE)
- CWE-22
- Known exploited
- Not in CISA's KEV catalog
- EPSS (exploitation in the next 30 days)
- Not loaded for this CVE
- Assigned by
- GitHub_M
- NVD analysis
- Awaiting Analysis
- Record last updated
- Oct 20, 2026
- First seen by InfoSec Signals
- Oct 20, 2026
Affected products
vitest-dev vitest vitest_dev:vitest (from the name) | from 4.1.11, < 4.1.12; from 5.0.0-rc.2, < 5.0.3 | CNA record |
@vitest mocker vitest:mocker (from the name) | from 4.1.11, < 4.1.12; from 5.0.0-rc.2, < 5.0.3 | CNA record |
References
- https://github.com/vitest-dev/vitest/security/advisories/GHSA-xp26-3454-mjgpx-refsource-confirm
- https://github.com/vitest-dev/vitest/commit/15cc006aa9f8683dc5f7e895d011fa7dc751ce35x-refsource-misc
- https://github.com/vitest-dev/vitest/commit/b825313243dc55757e8d7c0f9e7a792135e13473x-refsource-misc
- https://github.com/vitest-dev/vitest/releases/tag/v4.1.12x-refsource-misc
- https://github.com/vitest-dev/vitest/releases/tag/v5.0.3x-refsource-misc
The CVE record on cve.org NVD's entry
The CVE record is authoritative. Products marked “from the name” were identified from the CNA's free-text names, not a CPE, and are matched less certainly. This product uses the NVD API but is not endorsed or certified by the NVD.