PatchSiren

PatchSiren cyber security CVE debrief

CVE-2026-14631 webpack-dev-server CVE debrief

CVE-2026-14631 is a denial of service vulnerability in webpack-dev-server versions 5.2.5 and earlier. An unauthenticated peer can cause the server to crash by sending a normal HTTP request with a malformed Host header or a WebSocket upgrade to the default /ws endpoint with a malformed Origin header. The impact is limited to availability of the development server, with no data disclosure or code execution. This vulnerability has a CVSS score of 5.3 and a severity of MEDIUM.

Vendor
webpack-dev-server
Product
Unknown
CVSS
MEDIUM 5.3
CISA KEV
Not listed in stored evidence
Original CVE published
2026-07-03
Original CVE updated
2026-07-07
Advisory published
2026-07-03
Advisory updated
2026-07-07

Who should care

Developers and administrators using webpack-dev-server versions 5.2.5 and earlier should be aware of this vulnerability and take steps to mitigate it. This includes upgrading to webpack-dev-server 5.2.6 or later, and keeping the dev server bound to localhost (the default) and not exposing it to untrusted networks. Operators, platform teams, and security teams should review affected deployments and plan for remediation.

Technical summary

The vulnerability exists in the host-validation path of webpack-dev-server, where an uncaught exception occurs when a malformed Host header or Origin header is received. This causes the dev server to crash. The vulnerability has a CVSS score of 5.3 and a severity of MEDIUM. It affects webpack-dev-server versions 5.2.5 and earlier. Developers should verify affected product deployments and review official advisories for mitigation guidance, focusing on upgrading to webpack-dev-server 5.2.6 or later and ensuring the dev server is bound to localhost by default, not exposing it to untrusted networks.

Defensive priority

Medium priority should be given to patching or mitigating this vulnerability, as it can cause denial of service attacks on development servers.

Recommended defensive actions

  • Upgrade to webpack-dev-server 5.2.6 or later
  • Keep the dev server bound to localhost (the default)
  • Do not expose the dev server to untrusted networks
  • Review compensating controls for exposed systems while remediation is scheduled and verified
  • Check relevant monitoring, detection, and logs for exposed assets that need extra review
  • Track exceptions, retest remediated assets, and close the item only after evidence is documented
  • Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up

Evidence notes

The CVE record was published on 2026-07-03T18:16:24.687Z and last modified on 2026-07-07T15:08:59.667Z. The NVD entry is currently Analyzed. Evidence is limited to CVE and NVD information. Defenders should verify affected product deployments and review official advisories.

Sources and references

Verified primary and authoritative sources

  • CVE-2026-14631 CVE Program record

    Publisher, destination, and source semantics verified

    URL: https://www.cve.org/CVERecord?id=CVE-2026-14631

    CVE Program - Official CVE Program record with source-provided CVE metadata.

  • CVE-2026-14631 NVD vulnerability detail

    Publisher, destination, and source semantics verified

    URL: https://nvd.nist.gov/vuln/detail/CVE-2026-14631

    NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.

Supplemental references

  • Mitigation or vendor reference

    Unverified legacy reference

    URL: https://cna.openjsf.org/security-advisories.html

    ce714d77-add3-4f53-aff5-83d477b104bb - Third Party Advisory

  • Mitigation or vendor reference

    Unverified legacy reference

    URL: https://github.com/webpack/webpack-dev-server/security/advisories/GHSA-m28w-2pqf-7qgj

    ce714d77-add3-4f53-aff5-83d477b104bb - Mitigation, Vendor Advisory, Patch

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.