GHSA-g84c-rxfj-3j2c: Path Traversal

Published Sep 29, 2026
·
Updated

[!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

- CVE-2024-29180 (GHSA-wr3j-pwj9-hqq6), the earlier path traversal in the same component that this issue bypasses.

Affected Software

2 affected componentsFixes available
npm/webpack-dev-middleware<7.4.5
7.4.6
npm/webpack-dev-middleware>=8.0.0<8.3.0
8.3.0

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade npm/webpack-dev-middleware to a version that resolves this vulnerability.

    Fixed in 7.4.6
  2. Upgrade

    Upgrade npm/webpack-dev-middleware to a version that resolves this vulnerability.

    Fixed in 8.3.0
  3. Upgrade

    Upgrade webpack-dev-middleware to a version that resolves this vulnerability.

    Fixed in 8.3.0
  4. Configuration

    Configure publicPath with a trailing slash, for example /assets/ instead of /assets.

    webpack-dev-middleware publicPath = trailing slash

Event History

Sep 29, 2026
Advisory Published
via GitHub·04:59 PM
Data Sourced
via GitHub·04:59 PM
DescriptionSeverityWeaknessAffected Software

Frequently Asked Questions

1

Which deployments are exposed?

Applications that serve webpack-dev-middleware directly or through webpack-dev-server are affected when their configured publicPath does not end with a slash.

2

Does exploitation require authentication or special access?

No. An unauthenticated requester can read files outside the configured output root by sending a request that shares the publicPath prefix but is not actually beneath it.

3

How can I identify a potentially affected configuration?

Inspect the webpack-dev-middleware publicPath setting. A value without a trailing slash, such as /assets, is potentially affected; requests resembling /assets../secret can bypass the intended containment check.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203