Is CVE-2026-112950 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-112950 being exploited in the wild.

How severe is CVE-2026-112950?

Medium severity, with a CVSS score of 5.9, published 20 October 2026.

Which products and versions are affected?

@vitest/mocker (npm) >= 4.1.11, < 4.1.12, SEMVER:introduced=4.1.11,fixed=4.1.12; Vitest 4.1.11 until 4.1.12, 5.0.3.

Is there a fix for CVE-2026-112950?

Yes. @vitest/mocker (npm): upgrade to 4.1.12 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-112950 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2026-112950?

Check whether you run @vitest/mocker (npm) or Vitest at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-112950: Vitest path traversal via backslash interpretation on Windows

Q: Is there a fix for CVE-2026-112950?

Yes. @vitest/mocker (npm): upgrade to 4.1.12 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

Q: How is CVE-2026-112950 attacked?

It is attacked over the network, in a software library.

Q: Am I affected by CVE-2026-112950?

Check whether you run @vitest/mocker (npm) or Vitest at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-112950 · Severity: medium · CVSS 5.9 · Published 2026-10-20

Vitest is a testing framework for JavaScript and TypeScript projects. On Windows systems, an attacker who can reach the Vite development server can exploit a difference in how path separators are handled to read files outside the intended server restrictions, potentially accessing sensitive project files or secrets.

Technologies: @vitest/mocker (npm), Vitest. Vendors: npm, Vitest.

Quick answers

Is CVE-2026-112950 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-112950 being exploited in the wild.
How severe is CVE-2026-112950?: Medium severity, with a CVSS score of 5.9, published 20 October 2026.
Which products and versions are affected?: @vitest/mocker (npm) >= 4.1.11, < 4.1.12, SEMVER:introduced=4.1.11,fixed=4.1.12; Vitest 4.1.11 until 4.1.12, 5.0.3.
Is there a fix for CVE-2026-112950?: Yes. @vitest/mocker (npm): upgrade to 4.1.12 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-112950 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2026-112950?: Check whether you run @vitest/mocker (npm) or Vitest at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

@vitest/mocker (npm): upgrade to 4.1.12 or later
```
npm install @vitest/mocker@4.1.12
```

Technical details

The vulnerability exists in packages/mocker/src/node/interceptorPlugin.ts where the isFileLoadingAllowed function and filesystem read operations interpret backslashes differently on Windows. An attacker can register a redirect mock containing backslash path traversal sequences that POSIX path joining preserves; the later filesystem read then interprets these backslashes as path separators, bypassing server.fs.allow restrictions and allowing access to files the Vitest process can read.

Affected products

Vitest Vitest 4.1.11 until 4.1.12, 5.0.3

Identifiers

CVE-2026-112950
GHSA-xp26-3454-mjgp

Timeline

2026-10-20: disclosed

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.