GitHub Advisoryadvisory · npm

GHSA-79cf-xcqc-c78w webpack-dev-server vulnerable to cross-origin source code exposure on non-HTTPS origins

MEDIUM Published 2026-05-18 Modified 2026-05-18 Official page ↗
Aliases
CVE-2026-6402
Ecosystem
npm
Packages
webpack-dev-server
Severity
Moderate
CVSS vector
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:N/A:N
Weaknesses
CWE-749
Reviewed
2026-05-18

Affected packages

• npm webpack-dev-server: < 5.2.4 → fixed in 5.2.4

Description

Impact When webpack-dev-server is running on a non-HTTPS origin (the default), cross-origin requests from malicious websites can load the dev server's JavaScript bundles via `` tags. The fix introduced in v5.2.1 (CVE-2025-30359) relied on `Sec-Fetch-Mode` and `Sec-Fetch-Site` request headers to block these requests, but browsers only send these headers for potentially trustworthy origins. Over plain HTTP, the headers are absent and the check is bypassed. An attacker who knows the dev server's host, port, and output path can exfiltrate all module source code by intercepting the webpack runtime's module registration. This does not affect Chrome 142+ (and other Chromium-based browsers) due to local network access restrictions. Patches Patched in webpack-dev-server >= 5.2.4 by setting `Cross-Origin-Resource-Policy: same-origin` on responses. Workarounds Run the dev server with HTTPS enabled (`--https` or `server.type: 'https'` in config). Resources • GHSA-4v9v-hfq4-rm2v (CVE-2025-30359) - original vulnerability • GHSA-9jgg-88mc-972h (CVE-2025-30360) - prior bypass

Related

Alias · CVE (1)

  • CVE-2026-6402 webpack-dev-server versions up to and including 5.2.3 are vulnerable to cross-origin source code exposure when serving over a… vulnerability

Weakness · CWE (1)

  • CWE-749 Exposed Dangerous Method or Function weakness

References