Vulnerability Database · PyPI · werkzeug · Version

werkzeug 2.3.2

2.3.2 is affected by 17 vulnerabilities.

The vulnerabilities that cover this exact version are listed below with the fixed version to move to. The upgrade Vulert recommends: 3.1.9.

Critical 0 High 4 Medium 11 Low 0 Unrated 2

Released 28 Apr 2023 Licence BSD-3-Clause Also known from other sources 16 Newer releases 106 Database updated 23/Oct/2026

Release and licence data published by PyPI. 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 Vulnerabilities affecting this version

werkzeug 2.3.2 vulnerabilities

17 vulnerabilities cover werkzeug 2.3.2. Scroll the table for all of them, or open the full list in the database.

Vulnerability Severity Fixed version Disclosed
CVE-2024-49767: Werkzeug Resource Exhaustion Vulnerability in Multipart Form Data Parsing 7.5 high 3.0.6 13 Jul 2026
CVE-2024-34069: Werkzeug Debugger Remote Code Execution Vulnerability 7.5 high 3.0.3 07 Jul 2026
CVE-2024-49767: Werkzeug Resource Exhaustion Vulnerability in Multipart Form Parsing 7.5 medium 3.0.6 25 Oct 2024
Werkzeug Debugger Remote Execution Vulnerability in werkzeug 7.5 high 3.0.3 06 May 2024
CVE-2023-46136: Denial of Service Vulnerability in Werkzeug 7.5 high f3c803b3ade485a45f12b6d6617595350c0f03e2 25 Oct 2023
CVE-2026-102598: Werkzeug Vulnerability Allows Access to Windows Special Device Names 6.3 medium 3.1.9 15 Oct 2026
CVE-2026-102598: Werkzeug Vulnerability in safe_join Function Allows Access to Windows Special Device Names 6.3 medium 3.1.9 05 Oct 2026
CVE-2025-66221: Werkzeug Vulnerability in safe_join() Allows Access to Windows Special Device Names 6.3 medium 3.1.4 07 Jul 2026
CVE-2024-49766: Werkzeug Unsafe Path Handling on Windows 6.3 medium 3.0.6 07 Jul 2026
CVE-2026-27199: Werkzeug Vulnerability in safe_join Function Allows Access to Windows Special Device Names 6.3 medium 3.1.6 19 Feb 2026
CVE-2026-21860: Werkzeug Vulnerability in safe_join Function Allows Exploitation of Windows Special Device Names 6.3 medium 3.1.5 08 Jan 2026
CVE-2025-66221: Werkzeug Vulnerability in safe_join() Allows Access to Windows Special Device Names 6.3 medium 3.1.4 02 Dec 2025
CVE-2024-49766: Werkzeug Path Traversal Vulnerability on Windows 6.3 medium 3.0.6 25 Oct 2024
CVE-2026-21860: Werkzeug Vulnerability in safe_join Function Allows Exploitation of Windows Special Device Names 5.3 medium 3.1.5 07 Jul 2026
CVE-2026-27199: Werkzeug Safe Join Function Vulnerability on Windows 5.3 medium 3.1.6 21 Feb 2026
CVE-2023-25577: Denial of Service Vulnerability in Werkzeug N/A unrated 517cac5a804e8c4dc4ed038bb20dacd038e7a9f1 14 Feb 2023
CVE-2022-29361: HTTP Request Smuggling in Pallets Werkzeug N/A unrated 9a3a981d70d2e9ec3344b5192f86fcaf3210cd85 25 May 2022

Looking for another version, or everything Vulert holds for werkzeug?

All versions → Full vulnerability list →

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 werkzeug 2.3.2

Is werkzeug 2.3.2 vulnerable?

Yes. 17 vulnerabilities in the Vulert database cover werkzeug 2.3.2: 0 critical, 4 high, 11 medium and 0 low, plus 2 not yet rated. The upgrade Vulert recommends is 3.1.9, and each entry above names the fixed version to move to.

Which version of werkzeug should I use instead of 2.3.2?

3.1.9 is the version Vulert recommends for this release line. The version table on the package page lists every release with the vulnerabilities recorded against it.

Is 2.3.2 the latest release of werkzeug?

No. 2.3.2 was published 28 Apr 2023, and newer releases exist. Newer is not automatically safer — the version table on the package page shows what each release carries.

How do I monitor werkzeug for upcoming vulnerabilities?

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