webpack-dev-middleware
Affected
- introduced
8.0.0, fixed8.3.0(semver)
Fixed versions
8.3.0
Fix
- Fixed version
8.3.0npm install [email protected]
Advisory
Also known as: CVE-2026-76844
webpack-dev-middleware vulnerable to Path Traversal via non-slash-terminated publicPath
> [!IMPORTANT]
> CVE-2026-76844 was assigned and published for this issue by VulnCheck on 2026-08-24 without prior coordination with the webpack maintainers or the OpenJS Foundation, which holds the CVE Numbering Authority scope for webpack projects. Neither the maintainers nor the OpenJS CNA were notified before publication, and no fix was available at that time. This advisory is the coordinated record produced by the webpack maintainers and the OpenJS Foundation CNA.
Impact
webpack-dev-middleware resolves a request to a local file in getFilenameFromUrl. When the configured publicPath has no trailing slash (for example /assets), a request that shares that prefix without being under it (for example /assets../secret) still passes the containment check, and the .. guard does not catch it because it runs on the path before the publicPath prefix is stripped. The stripped remainder then escapes the configured output directory once joined, so an unauthenticated request can read files outside the output root. Applications serving webpack-dev-middleware (directly or via webpack-dev-server) with a publicPath that does not end in a slash are affected. A development server reachable on the network can be attacked with a single request and no victim interaction.
Patches
Patched in webpack-dev-middleware 8.3.0. There is no backport to the 5.x, 6.x, or 7.x lines; users on those lines should upgrade to 8.3.0 or later.
Workarounds
Configure publicPath with a trailing slash (for example /assets/ instead of /assets), or upgrade to a patched version.
References
High Basis: The source's own band: HIGH
8.0.0, fixed 8.3.0 (semver)8.3.0
8.3.0npm install [email protected]0, fixed 7.4.6 (semver)7.4.6
7.4.6npm install [email protected]Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0