CVE-2026-76844
Description
A flaw was found in webpack-dev-middleware. An unauthenticated remote attacker can exploit this vulnerability to read arbitrary files outside the intended base directory on the host system, leading to unauthorized information disclosure. This issue occurs when the public path is configured without a trailing slash, allowing crafted Uniform Resource Locators (URLs) to bypass path traversal checks before the prefix is stripped. The vulnerability affects deployments where the middleware serves files directly from the physical filesystem.
Statement
A path traversal vulnerability exists in the getFilenameFromUrl function of webpack-dev-middleware. When publicPath is configured without a trailing slash, the middleware performs string prefix matching and checks for .. segments before stripping the prefix, allowing an unauthenticated remote attacker to request crafted URLs (such as /assets../secret) and read arbitrary files one directory above the output directory when serving from the physical filesystem via writeToDisk or a custom outputFileSystem.
Mitigation
Append a trailing slash to the `publicPath` option in the webpack-dev-middleware configuration (for example, changing `publicPath: '/assets'` to `publicPath: '/assets/'`). Additionally, disable `writeToDisk` or avoid serving directly from the physical filesystem if not strictly required, and ensure the development server is not exposed to untrusted networks.
Common Vulnerability Scoring System (CVSS) Score Details
Info alert:Important note
CVSS scores for open source components depend on vendor-specific factors (e.g. version or build chain). Therefore, Red Hat's score and impact rating can be different from NVD and other vendors. Red Hat remains the authoritative CVE Naming Authority (CNA) source for its products and services (see Red Hat classifications).
CVSS v3 Score Breakdown
| Red Hat | NVD | cve.org | |
|---|---|---|---|
| Base Score | 7.4 | N/A | 7.4 |
| Attack Vector | Network | N/A | Network |
| Attack Complexity | Low | N/A | Low |
| Privileges Required | None | N/A | None |
| User Interaction | Required | N/A | Required |
| Scope | Changed | N/A | Changed |
| Confidentiality | High | N/A | High |
| Integrity Impact | None | N/A | None |
| Availability Impact | None | N/A | None |
Vector
Red Hat: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:N/A:N
cve.org: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:N/A:N
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.