VulnerabilityPublished 20 Oct 2026

CVE-2026-112950: vitest · Path Traversal

Affects vitestSource CVE Database V5

Not known to be exploited · CVSS 5.9 Medium : upgrade to 5.0.3 or 4.1.12 when convenient.

Data as of 26 Oct 2026, 14:05 UTC

CVSS 3.1 base score

5.9Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.4% chance of exploitation in 30 days – higher than 39% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 5.0.3, 4.1.12

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

Attack Vector: Network
Attack Complexity: High
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: None
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: High: A successful attack depends on conditions beyond the attacker's control. That is, a successful attack cannot be accomplished at will, but requires the attacker to invest in some measurable amount of effort in preparation or execution against the vulnerable component before a successful attack can be expected. For example, a successful attack may require an attacker to: gather knowledge about the environment in which the vulnerable target/component exists; prepare the target environment to improve exploit reliability; or inject themselves into the logical network path between the target and the resource requested by the victim in order to read and/or modify network communications (e.g., a man in the middle attack).
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 20 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade vitest and mocker and vitest-dev/vitest to 5.0.3 or 4.1.12.

Affected software

Product	Affected	Fixed in
vitest-devvitest	Affected >=5.0.0-rc.2 <5.0.3	Fixed in 5.0.3
vitest-devvitest	Affected >=4.1.11 <4.1.12	Fixed in 4.1.12
@vitestmocker	Affected >=5.0.0-rc.2 <5.0.3	Fixed in 5.0.3
@vitestmocker	Affected >=4.1.11 <4.1.12	Fixed in 4.1.12
npmvitest-dev/vitest`pkg:npm/vitest-dev/vitest`Other threats	Affected >=4.1.11 <4.1.12 >=5.0.0-rc.2 <5.0.3	Fixed in 4.1.12 5.0.3

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade Vitest to version 4.1.12 or later, or 5.0.3 or later, where this path traversal vulnerability is fixed. No other mitigation is indicated by the vendor advisory. Patch status is confirmed fixed in these versions.

Description

CVE-2026-112950 is a path traversal vulnerability in the Vitest testing framework for JavaScript and TypeScript. It affects versions from 4.1.11 up to but not including 4.1.12, and from 5.0.0-rc.2 up to but not including 5.0.3. On Windows, the issue arises because backslash characters in paths are interpreted inconsistently, allowing a client connected to the Vite dev server to read files outside the intended allowed directory. This vulnerability is fixed in versions 4.1.12 and 5.0.3.

Impact

An unauthenticated remote attacker who can access the Vite development server on Windows can exploit this vulnerability to read arbitrary files accessible to the Vitest process outside the intended restricted directory. This leads to confidentiality breaches but does not affect integrity or availability. The CVSS 3.1 score is 5.9 (medium severity) with network attack vector, high attack complexity, no privileges required, no user interaction, and impact limited to confidentiality.

Summary

Vitest versions >=4.1.11 <4.1.12 and >=5.0.0-rc.2 <5.0.3 contain a path traversal vulnerability (CWE-22) due to improper handling of backslash characters in filesystem paths on Windows. The isFileLoadingAllowed function and filesystem read operations interpret backslashes differently, enabling a client able to reach the Vite dev server to register a redirect mock with backslash traversal sequences. This causes POSIX path joining to preserve Windows backslash traversal, which the filesystem read then interprets as path separators, allowing unauthorized file reads outside the configured server.fs.allow directory. The vulnerability is resolved in versions 4.1.12 and 5.0.3.

CWE-22Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') (opens in a new tab)
Base weaknessLikelihood of exploit: HighCWE Top 25 (2025): #6OWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory.
Implementation · Input Validation
Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does.
Architecture and Design
For any security checks that are performed on the client side, ensure that these checks are duplicated on the server side, in order to avoid CWE-602. Attackers can bypass the client-side checks by modifying values after the checks have been performed, or by changing the client to remove the client-side checks…
Implementation · Input Validation
Inputs should be decoded and canonicalized to the application's current internal representation before being validated (CWE-180). Make sure that the application does not decode the same input twice (CWE-174).
OWASP Cheat Sheets
Authorization (opens in a new tab)
OWASP ASVS 4.0.3
V12.3.1 (opens in a new tab)
Attack patterns
Path Traversal (opens in a new tab)
Using Slashes and URL Encoding Combined to Bypass Validation Logic (opens in a new tab)
Manipulating Web Input to File System Calls (opens in a new tab)
Using Escaped Slashes in Alternate Encoding (opens in a new tab)
Using Slashes in Alternate Encoding (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 20 Oct 2026, 16:03 UTC

WeaknessesCWE-22

Technical details

References

Community reviews

Related threats