werkzeug vulnerabilities

The comprehensive WSGI web application library.

Registry
PyPI
Latest
3.1.9
License
BSD-3-Clause

15 known advisories

The latest version, 3.1.9, is not affected by any of them. Projects on older versions may be.

Update to the latest version: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

Security advisories for werkzeug

  • 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
  • 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
  • LowCVE-2022-29361PYSEC-2022-20325 May 2022

    No summary published

    Affected
    <2.1.1
    Fixed in
    2.1.1
  • HighCVE-2019-14322GHSA-j544-7q9p-6xp824 May 2022

    Pallets Werkzeug vulnerable to Path Traversal

    Affected
    <0.15.5
    Fixed in
    0.15.5
  • MediumCVE-2016-10516GHSA-h2fp-xgx6-xh6f14 May 2022

    Pallets Werkzeug cross-site scripting vulnerability

    Affected
    <0.11.11
    Fixed in
    0.11.11
  • MediumCVE-2020-28724GHSA-3p3h-qghp-hvh220 Apr 2021

    Open Redirect in werkzeug

    Affected
    <0.11.6
    Fixed in
    0.11.6
  • HighCVE-2019-14806GHSA-gq9m-qvpx-68hc21 Aug 2019

    Pallets Werkzeug Insufficient Entropy

    Affected
    <0.15.3
    Fixed in
    0.15.3

Is your werkzeug version vulnerable?

Which of your client projects still run an old werkzeug?

NPMscan reads the requirements.txt, poetry.lock, uv.lock and Pipfile.lock in every GitHub repo you pick and checks each installed version against these advisories, including the packages your packages pull in. Each finding comes with the command that fixes it.

Other PyPI packages

Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily. Package details from the PyPI registry.