CVE-2026-112950
Description
A flaw was found in the Vitest mocker component when running on Windows systems. A remote attacker with access to the development server can exploit inconsistent path separator handling between file access validation and filesystem operations. By registering mock requests containing backslash directory traversal sequences, the attacker can bypass directory restrictions to read arbitrary files accessible to the application process.
Statement
This vulnerability is rated Moderate severity because it requires network reachability to an active development server and is strictly limited to Windows operating systems. The vulnerability stems from Windows treating backslashes as path delimiters, which allows traversal sequences to evade POSIX-based path validation. Because Red Hat enterprise products run exclusively on Linux-based environments where backslashes are not interpreted as directory separators, Red Hat platforms are not impacted.
Understanding the Weakness (CWE)
Integrity,Confidentiality,Availability
Technical Impact: Execute Unauthorized Code or Commands
The attacker may be able to create or overwrite critical files that are used to execute code, such as programs or libraries.
Integrity
Technical Impact: Modify Files or Directories
The attacker may be able to overwrite or create critical files, such as programs, libraries, or important data. If the targeted file is used for a security mechanism, then the attacker may be able to bypass that mechanism. For example, appending a new account at the end of a password file may allow an attacker to bypass authentication.
Confidentiality
Technical Impact: Read Files or Directories
The attacker may be able to read the contents of unexpected files and expose sensitive data. If the targeted file is used for a security mechanism, then the attacker may be able to bypass that mechanism. For example, by reading a password file, the attacker could conduct brute force password guessing attacks in order to break into an account on the system.
Availability
Technical Impact: DoS: Crash, Exit, or Restart
The attacker may be able to overwrite, delete, or corrupt unexpected critical files such as programs, libraries, or important data. This may prevent the product from working at all and in the case of protection mechanisms such as authentication, it has the potential to lock out product users.
Frequently Asked Questions
Not sure what something means? Check out our Security Glossary.
Want to get errata notifications? Sign up here.
