webpack-dev-server vulnerable to cross-site request forgery via internal developer endpoints
Published 20 Jul 2026 · Updated 10 Sept 2026
Affected package
- Affected
- <5.2.6
- Fixed in
- 5.2.6
npm install webpack-dev-server@5.2.6Details
Impact
The internal /webpack-dev-server/open-editor and /webpack-dev-server/invalidate endpoints perform state-changing actions on any GET request, without verifying that the request originated from the dev server's own page. Any website a developer visits while the dev server is running can trigger them cross-origin with no interaction beyond the visit.
An attacker can open an arbitrary existing local file in the developer's editor, including files outside the project root (e.g. ~/.ssh/config). The file's contents are not returned to the attacker. Repeated requests can also spawn editor processes and force recompilations, degrading the developer's machine.
Patches
Fixed in webpack-dev-server 5.2.6 by rejecting cross-site requests to the /webpack-dev-server/open-editor and /webpack-dev-server/invalidate endpoints (see PR #5698).
Workarounds
None
Is GHSA-f5vj-f2hx-8m93 in any of your client repos?
Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected webpack-dev-server, and gives you the command that fixes it.
References
- Linkgithub.com/webpack/webpack-dev-server/security/advisories/GHSA-f5vj-f2hx-8m93
- Advisorynvd.nist.gov/vuln/detail/CVE-2026-14620
- Linkgithub.com/webpack/webpack-dev-server/pull/5698
- Linkgithub.com/webpack/webpack-dev-server/commit/80cd9eea54975fe632a518d8bd902a260f374e7c
- Linkcna.openjsf.org/security-advisories.html
- Packagegithub.com/webpack/webpack-dev-server
- Linkgithub.com/webpack/webpack-dev-server/releases/tag/v5.2.6
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.