Cross-Site Request Forgery (CSRF) in webpack-dev-server (CVE-2026-14620)
Summary
Vulnerability in webpack-dev-server (CVE-2026-14620). Risk of unauthorized operations or information disclosure. Exploitable via GET. Mitigation: upgrade to 5.2.6 or later.
Original description
The description as published by the source.
webpack-dev-server versions 5.2.5 and earlier expose two internal developer endpoints, /webpack-dev-server/open-editor and /webpack-dev-server/invalidate, that 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 these endpoints 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, and repeated requests can spawn editor processes and force recompilations that degrade the developer's machine. Patches: upgrade to webpack-dev-server 5.2.6. Workarounds: none.
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-14620 has been found in webpack-dev-server.
Attackers can target a specific entry point like GET over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 4.7/10.
What to do: upgrade webpack-dev-server to 5.2.6 or later.
If unsure, ask your IT team or search "webpack-dev-server CVE-2026-14620" on the vendor's site.
CVE-2026-14620 (webpack-dev-server) — CWE-352 / CVSS v3 4.7
Attack vector: remote (network-reachable) / unauthenticated
Attack surface: GET
Patched: 5.2.6 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
CSRF (CWE-352) exists in webpack-dev-server. Attackers reach the vulnerable code path via GET without authentication.
Check the vendor advisory for the affected versions of webpack-dev-server. Attack surface: GET.
Severity: Medium (CVSS 4.7/10). Risk of unauthorized operations or information disclosure.
Update to 5.2.6.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'webpack-dev-server' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'webpack-dev-server' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
webpack-dev-serverを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade webpack-dev-server to 5.2.6ステージング環境で 5.2.6 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory cna.openjsf.org
- advisory github.com
- advisory nvd.nist.gov
- advisory github.com
- web github.com
- web github.com
- web github.com
- web github.com