VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

webpack-dev-server: vulnerability history, versions and safety

webpack-dev-server is a package in the npm ecosystem. Vulert records 7 vulnerabilities for it across 116 releases, from Jan 2019 to Jul 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
7 vulnerabilities recorded H1 M6
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
4 in the last 12 months

Most recent disclosure 20 Jul 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all webpack-dev-server vulnerabilities

Vulert verdict on webpack-dev-server 6.1.0 i

Updated on 23 Oct 2026

Good news: 6.1.0, the version you would install today, has no known vulnerabilities. Older releases do — the table below lists all 7.

Package health score 76/100
  • Security Some issues to review
  • Maintenance Sustainable
  • Popularity Widely used
  • Community Moderate

What to do: Stay on 6.1.0 or newer. This can change: a vulnerability disclosed tomorrow can affect 6.1.0 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →

  • Current release 6.1.0 — unaffected i
  • Vulnerabilities on record 7 over 7 years · 4 in the last year i
  • Latest disclosure 20 Jul 2026 i
  • Highest CVSS 7.5 i
  • With no published fix 0 i
  • Depended on by 277 packages i
  • Stars 7,843 i
  • OpenSSF scorecard 5/10 i
  • Last release this month i
  • Licence MIT i

Version list, release dates, licence and dependants published by the npm registry, refreshed 22 Oct 2026. Licence information is not legal advice.

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Every version Vulert tracks for webpack-dev-server, newest first, with the vulnerabilities recorded against each one. A version showing none has no vulnerability in the Vulert database — open it for the full picture on that release.

i
Version Released Vulert vulnerabilities Licence Fix published Details
6.1.0 18 Oct 2026 none MIT — Details →
5.2.7 18 Oct 2026 none MIT — Details →
6.0.0 03 Jul 2026 none MIT — Details →
5.2.6 02 Jul 2026 none MIT — Details →
5.2.5 12 Jun 2026 M2 MIT Yes Details →
5.2.4 11 May 2026 M3 MIT Yes Details →
5.2.3 12 Jan 2026 M4 MIT Yes Details →
5.2.2 03 Jun 2025 M4 MIT Yes Details →
5.2.1 26 Mar 2025 M4 MIT Yes Details →
5.2.0 11 Dec 2024 M6 MIT Yes Details →
5.1.0 03 Sep 2024 M6 MIT Yes Details →
4.15.2 20 Mar 2024 M6 MIT Yes Details →
5.0.4 19 Mar 2024 M6 MIT Yes Details →
5.0.3 12 Mar 2024 M6 MIT Yes Details →
5.0.2 16 Feb 2024 M6 MIT Yes Details →
5.0.1 13 Feb 2024 M6 MIT Yes Details →
5.0.0 12 Feb 2024 M6 MIT Yes Details →
4.15.1 09 Jun 2023 M6 MIT Yes Details →
4.15.0 07 May 2023 M6 MIT Yes Details →
4.14.0 06 May 2023 M6 MIT Yes Details →
4.13.3 15 Apr 2023 M6 MIT Yes Details →
4.13.2 31 Mar 2023 M6 MIT Yes Details →
4.13.1 18 Mar 2023 M6 MIT Yes Details →
4.13.0 17 Mar 2023 M6 MIT Yes Details →
4.12.0 14 Mar 2023 M6 MIT Yes Details →
4.11.1 19 Sep 2022 M6 MIT Yes Details →
4.11.0 07 Sep 2022 M6 MIT Yes Details →
4.10.1 29 Aug 2022 M6 MIT Yes Details →
4.10.0 10 Aug 2022 M6 MIT Yes Details →
4.9.3 29 Jun 2022 M6 MIT Yes Details →
4.9.2 06 Jun 2022 M6 MIT Yes Details →
4.9.1 31 May 2022 M6 MIT Yes Details →
4.9.0 04 May 2022 M6 MIT Yes Details →
4.8.1 06 Apr 2022 M6 MIT Yes Details →
4.8.0 05 Apr 2022 M6 MIT Yes Details →
4.7.4 02 Feb 2022 M6 MIT Yes Details →
4.7.3 11 Jan 2022 M6 MIT Yes Details →
4.7.2 29 Dec 2021 M6 MIT Yes Details →
4.7.1 22 Dec 2021 M6 MIT Yes Details →
4.7.0 21 Dec 2021 M6 MIT Yes Details →
4.6.0 25 Nov 2021 M6 MIT Yes Details →
4.5.0 13 Nov 2021 M6 MIT Yes Details →
3.11.3 08 Nov 2021 M6 MIT Yes Details →
4.4.0 27 Oct 2021 M6 MIT Yes Details →
4.3.1 04 Oct 2021 M6 MIT Yes Details →
4.3.0 25 Sep 2021 M6 MIT Yes Details →
4.2.1 13 Sep 2021 M6 MIT Yes Details →
4.2.0 09 Sep 2021 M6 MIT Yes Details →
4.1.1 07 Sep 2021 M6 MIT Yes Details →
4.1.0 31 Aug 2021 M6 MIT Yes Details →
4.0.0 18 Aug 2021 M6 MIT Yes Details →
4.0.0-rc.1 17 Aug 2021 M6 MIT Yes Details →
4.0.0-rc.0 19 Jul 2021 M6 MIT Yes Details →
4.0.0-beta.3 06 May 2021 M6 MIT Yes Details →
4.0.0-beta.2 06 Apr 2021 M6 MIT Yes Details →
4.0.0-beta.1 23 Mar 2021 M6 MIT Yes Details →
3.11.2 13 Jan 2021 M6 MIT Yes Details →
3.11.1 29 Dec 2020 M6 MIT Yes Details →
4.0.0-beta.0 27 Nov 2020 M6 MIT Yes Details →
3.11.0 08 May 2020 M6 MIT Yes Details →
3.10.3 05 Feb 2020 M6 MIT Yes Details →
3.10.2 31 Jan 2020 M6 MIT Yes Details →
3.10.1 19 Dec 2019 M6 MIT Yes Details →
3.10.0 18 Dec 2019 M6 MIT Yes Details →
3.9.0 22 Oct 2019 M6 MIT Yes Details →
3.8.2 02 Oct 2019 M6 MIT Yes Details →
3.8.1 16 Sep 2019 M6 MIT Yes Details →
3.8.0 09 Aug 2019 M6 MIT Yes Details →
3.7.2 18 Jun 2019 M6 MIT Yes Details →
3.7.1 07 Jun 2019 M6 MIT Yes Details →
3.7.0 06 Jun 2019 M6 MIT Yes Details →
3.6.0 05 Jun 2019 M6 MIT Yes Details →
3.5.1 01 Jun 2019 M6 MIT Yes Details →
3.5.0 31 May 2019 M6 MIT Yes Details →
3.4.1 17 May 2019 M6 MIT Yes Details →
3.4.0 17 May 2019 M6 MIT Yes Details →
3.3.1 09 Apr 2019 M6 MIT Yes Details →
3.3.0 08 Apr 2019 M6 MIT Yes Details →
2.11.5 23 Mar 2019 H1 M6 MIT Yes Details →
2.11.4 22 Mar 2019 H1 M6 MIT Yes Details →
3.2.1 25 Feb 2019 M6 MIT Yes Details →
3.2.0 20 Feb 2019 M6 MIT Yes Details →
3.1.14 24 Dec 2018 M6 MIT Yes Details →
3.1.13 22 Dec 2018 M6 MIT Yes Details →
3.1.12 22 Dec 2018 M6 MIT Yes Details →
3.1.11 21 Dec 2018 M6 MIT Yes Details →
3.1.10 23 Oct 2018 H1 M6 MIT Yes Details →
3.1.9 24 Sep 2018 H1 M6 MIT Yes Details →
3.1.8 06 Sep 2018 H1 M6 MIT Yes Details →
3.1.7 29 Aug 2018 H1 M6 MIT Yes Details →
3.1.6 26 Aug 2018 H1 M6 MIT Yes Details →
2.11.3 22 Aug 2018 H1 M6 MIT Yes Details →
3.1.5 22 Jul 2018 H1 M6 MIT Yes Details →
3.1.4 02 May 2018 H1 M6 MIT Yes Details →
3.1.3 08 Apr 2018 H1 M6 MIT Yes Details →
3.1.2 07 Apr 2018 H1 M6 MIT Yes Details →
3.1.1 09 Mar 2018 H1 M6 MIT Yes Details →
3.1.0 27 Feb 2018 H1 M6 MIT Yes Details →
3.0.1-beta.0 26 Feb 2018 H1 M6 MIT Yes Details →
2.11.2 26 Feb 2018 H1 M6 MIT Yes Details →
3.0.0 25 Feb 2018 H1 M6 — Yes Details →
3.0.0-beta.2 17 Feb 2018 H1 M6 — Yes Details →
3.0.0-beta.1 14 Feb 2018 H1 M6 — Yes Details →
2.11.1 20 Jan 2018 H1 M6 — Yes Details →
2.11.0 14 Jan 2018 H1 M6 — Yes Details →
2.10.1 09 Jan 2018 H1 M6 — Yes Details →
2.10.0 06 Jan 2018 H1 M6 — Yes Details →
3.0.0-alpha6 19 Dec 2017 H1 M6 — Yes Details →
3.0.0-alpha5 09 Dec 2017 H1 M6 — Yes Details →
3.0.0-alpha4 09 Dec 2017 H1 M6 — Yes Details →
3.0.0-alpha3 09 Dec 2017 H1 M6 — Yes Details →
3.0.0-alpha2 08 Dec 2017 H1 M6 — Yes Details →
3.0.0-alpha1 08 Dec 2017 H1 M6 — Yes Details →
2.9.7 07 Dec 2017 H1 M6 — Yes Details →
2.9.6 06 Dec 2017 H1 M6 — Yes Details →
2.9.5 27 Nov 2017 H1 M6 — Yes Details →
2.9.4 02 Nov 2017 H1 M6 — Yes Details →
2.9.3 20 Oct 2017 H1 M6 — Yes Details →
2.9.2 15 Oct 2017 H1 M6 — Yes Details →
2.9.1 27 Sep 2017 H1 M6 — Yes Details →

The newest 120 of 228 versions Vulert tracks. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2019 1
  • 2025 2
  • 2026 4

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 4 of the 7 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for webpack-dev-server

The 5 most severe of 7 vulnerabilities recorded for this package

Search all 7 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2018-14732: Missing Origin Validation in webpack-dev-server 7.5 high 3.1.11 04 Jan 2019
CVE-2025-30360: webpack-dev-server Source Code Theft via Non-Chromium Browsers 6.5 medium 5.2.1 04 Jun 2025
CVE-2025-30359: webpack-dev-server Source Code Theft Vulnerability 5.3 medium 5.2.1 04 Jun 2025
CVE-2026-6402: webpack-dev-server Cross-Origin Source Code Exposure on Non-HTTPS Origins 5.3 medium 5.2.4 18 May 2026
CVE-2026-9595: webpack-dev-server Vulnerable to HMR WebSocket Interception via Permissive User Proxies 5.3 medium 5.2.5 17 Jun 2026

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About webpack-dev-server

Is webpack-dev-server safe to use?

Vulert records 7 vulnerabilities for webpack-dev-server in npm: 0 critical, 1 high, 6 medium and 0 low. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

What is webpack-dev-server's Vulert package health score?

Vulert scores webpack-dev-server 76/100, which reads as in good shape. The score weighs the vulnerability record (40), maintenance and release cadence (25), adoption from dependents and stars (20) and community signals such as the OpenSSF scorecard and forks (15).

Is the latest version of webpack-dev-server affected?

No. 6.1.0, the version you would install today, has no vulnerabilities on record against it. Earlier releases do — the version table above lists each release with what affects it.

How many vulnerabilities does webpack-dev-server have?

7 vulnerabilities are recorded for webpack-dev-server in the npm ecosystem: 0 critical, 1 high, 6 medium and 0 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new webpack-dev-server vulnerabilities disclosed?

4 vulnerabilities were recorded for webpack-dev-server in the last 12 months, and the oldest entry in this database dates to 04 Jan 2019. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of webpack-dev-server are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor webpack-dev-server for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the webpack-dev-server version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.