← Back
CVE-2026-14620
medium
CVSS 4.7
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.
AI summary snake-internal / snake-material-v2
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.
❓ What is the problem
**CSRF** (CWE-352) exists in webpack-dev-server. Attackers reach the vulnerable code path via ``GET`` without authentication.
📍 Affected scope
webpack-dev-server — . Attack surface: `GET`.
🔥 Severity
Severity: Medium (CVSS 4.7/10). Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **5.2.6**.
🛡️ Workaround
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
🔍 Detection
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 (7 steps)
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 し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade webpack-dev-server to 5.2.6ステージング環境で 5.2.6 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
npm
webpack-dev-server
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.2.6"}]}]
References
- web https://cna.openjsf.org/security-advisories.html
- web https://github.com/webpack/webpack-dev-server/security/advisories/GHSA-f5vj-f2hx-8m93
- web https://nvd.nist.gov/vuln/detail/CVE-2026-14620
- web https://github.com/webpack/webpack-dev-server/pull/5698
- web https://github.com/webpack/webpack-dev-server/commit/80cd9eea54975fe632a518d8bd902a260f374e7c
- web https://github.com/webpack/webpack-dev-server/releases/tag/v5.2.6
- web https://github.com/advisories/GHSA-f5vj-f2hx-8m93