Is werkzeug 2.2 vulnerable?

PyPI · 4 releases from 2.2.0 to 2.2.3 · latest werkzeug is 3.1.9 · checked 18 Nov 2026

Yes: 8 known advisories

Yes. werkzeug 2.2.3, the last 2.2 release, is affected by 8 known security advisories (1 high, 7 medium), including CVE-2024-34069, CVE-2026-102598, CVE-2026-27199. 2 more affect earlier 2.2.x releases. Upgrade to 3.1.9 or later to fix all of them.

Upgrade with:pip install 'werkzeug>=3.1.9'

Is your project on an affected werkzeug?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

Look after several Python apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie

Advisories affecting werkzeug 2.2.3

  • MediumCVE-2026-102598GHSA-g6x2-hccm-hh4m5 Oct 2026

    Werkzeug safe_join() allows Windows special device names

    Affected
    <3.1.9
    Fixed in
    3.1.9
  • MediumCVE-2026-27199GHSA-29vq-49wr-vm6x19 Feb 2026

    Werkzeug safe_join() allows Windows special device names

    Affected
    <3.1.6
    Fixed in
    3.1.6
  • MediumCVE-2026-21860GHSA-87hc-h4r5-73f78 Jan 2026

    Werkzeug safe_join() allows Windows special device names with compound extensions

    Affected
    <3.1.5
    Fixed in
    3.1.5
  • MediumCVE-2025-66221GHSA-hgf8-39gv-g3f22 Dec 2025

    Werkzeug safe_join() allows Windows special device names

    Affected
    <3.1.4
    Fixed in
    3.1.4
  • MediumCVE-2024-49767GHSA-q34m-jh98-gwm225 Oct 2024

    Werkzeug possible resource exhaustion when parsing file data in forms

    Affected
    >=2.0.0rc1 <3.0.6
    Fixed in
    3.0.6
  • MediumCVE-2024-49766GHSA-f9vj-2wh5-fj8j25 Oct 2024

    Werkzeug safe_join not safe on Windows

    Affected
    <3.0.6
    Fixed in
    3.0.6
  • HighCVE-2024-34069GHSA-2g68-c3qc-89856 May 2024

    Werkzeug debugger vulnerable to remote execution when interacting with attacker controlled domain

    Affected
    <3.0.3
    Fixed in
    3.0.3
  • MediumCVE-2023-46136GHSA-hrfv-mqp8-q5rw25 Oct 2023

    Werkzeug DoS: High resource usage when parsing multipart/form-data containing a large part with CR/LF character at the beginning

    Affected
    >=3.0.0 <3.0.1 · >=2.0.0rc1 <2.3.8
    Fixed in
    2.3.8, 3.0.1

Fixed within 2.2.x, affecting earlier releases

  • LowCVE-2023-23934GHSA-px8h-6qxv-m22q15 Feb 2023

    Incorrect parsing of nameless cookies leads to __Host- cookies bypass

    Affected
    <2.2.3
    Fixed in
    2.2.3
  • HighCVE-2023-25577GHSA-xg9f-g7g7-232315 Feb 2023

    High resource usage when parsing multipart form data with many fields

    Affected
    <2.2.3
    Fixed in
    2.2.3

Every werkzeug 2.2.x release

Affected: 2.2.0 to 2.2.3. Latest werkzeug: 3.1.9.

VersionKnown advisories
werkzeug 2.2.3CVE-2026-102598, CVE-2026-27199, CVE-2026-21860, CVE-2025-66221, CVE-2024-49767, CVE-2024-49766, CVE-2024-34069, CVE-2023-46136
werkzeug 2.2.2CVE-2026-102598, CVE-2026-27199, CVE-2026-21860, CVE-2025-66221, CVE-2024-49767, CVE-2024-49766, CVE-2024-34069, CVE-2023-46136, CVE-2023-23934, CVE-2023-25577
werkzeug 2.2.1CVE-2026-102598, CVE-2026-27199, CVE-2026-21860, CVE-2025-66221, CVE-2024-49767, CVE-2024-49766, CVE-2024-34069, CVE-2023-46136, CVE-2023-23934, CVE-2023-25577
werkzeug 2.2.0CVE-2026-102598, CVE-2026-27199, CVE-2026-21860, CVE-2025-66221, CVE-2024-49767, CVE-2024-49766, CVE-2024-34069, CVE-2023-46136, CVE-2023-23934, CVE-2023-25577

Which of your client projects are still on werkzeug 2.2?

NPMscan reads the lockfiles in every GitHub repo you pick, finds the exact werkzeug version each one installs, and checks it against these advisories. Each finding comes with the command that fixes it.

Other werkzeug versions

Advisory data from OSV.dev (opens OSV.dev in a new tab), which includes the GitHub Advisory Database. Release list from the PyPI registry. Refreshed daily.