Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
High, CVSS 7.4amended

Path traversal in webpack-dev-middleware

CVE-2024-29180GHSA-wr3j-pwj9-hqq6

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (webpack-dev-middleware 7.1.0, 6.1.2, 5.3.4), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
7.4 · CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:N/A:N
EPSS
  • CVE-2024-29180: 1.23% estimated exploitation activity in the next 30 days; percentile 68.86 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

Summary The webpack-dev-middleware middleware does not validate the supplied URL address sufficiently before returning the local file. It is possible to access any file on the developer's machine. Details The middleware can either work with the physical filesystem when reading the files or it can use a virtualized in-memory memfs filesystem. If writeToDisk configuration option is set to true, the physical filesystem is used: https://github.com/webpack/webpack-dev-middleware/blob/7ed24e0b9f53ad1562343f9f517f0f0ad2a70377/src/utils/setupOutputFileSystem.js#L21 The getFilenameFromUrl method is used to parse URL and build the local file path. The public path prefix is stripped from the URL, and the unsecaped path suffix is appended to the outputPath: https://github.com/webpack/webpack-dev-middleware/blob/7ed24e0b9f53ad1562343f9f517f0f0ad2a70377/src/utils/getFilenameFromUrl.js#L82 As the URL is not unescaped and normalized automatically before calling the midlleware, it is possible to use…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 2 · amended ·

    Amended from ghsa record GHSA-wr3j-pwj9-hqq6

  2. Revision 1 · created ·

    Published from osv record GHSA-wr3j-pwj9-hqq6

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2024-29180

Advisory: Path traversal in webpack-dev-middleware
IDs: CVE-2024-29180, GHSA-wr3j-pwj9-hqq6
Record: https://patchnext.com/advisories/cve-2024-29180 (revision 2, source checked 26 Oct 2026, 12:30 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.4)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: webpack-dev-middleware 7.1.0, 6.1.2, 5.3.4. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm webpack-dev-middleware: affected >= 7.0.0, < 7.1.0; >= 6.0.0, < 6.1.2; <= 5.3.3; fixed in 6.1.2, 7.1.0, 5.3.4

## Suggested inspection (read-only)
- `npm ls webpack-dev-middleware --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on webpack-dev-middleware.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-wr3j-pwj9-hqq6 (OSV record GHSA-wr3j-pwj9-hqq6 lists affected ranges: npm webpack-dev-middleware >=7.0.0 =6.0.0 =0 <5.3.4 (fixed))
- Verified: https://github.com/advisories/GHSA-wr3j-pwj9-hqq6 (GitHub-reviewed advisory GHSA-wr3j-pwj9-hqq6 lists affected ranges: npm webpack-dev-middleware >=7.0.0 =6.0.0 =0 <=5.3.3)

Commands are suggestions: review each one before running it.

Loading voting…