Is werkzeug 2.3 vulnerable?
PyPI · 9 releases from 2.3.0 to 2.3.8 · latest werkzeug is 3.1.9 · checked 18 Nov 2026
Yes: 7 known advisories
Yes. werkzeug 2.3.8, the last 2.3 release, is affected by 7 known security advisories (1 high, 6 medium), including CVE-2024-34069, CVE-2026-102598, CVE-2026-27199. 1 more affects earlier 2.3.x releases. Upgrade to 3.1.9 or later to fix all of them.
pip install 'werkzeug>=3.1.9'Is your project on an affected werkzeug?
Look after several Python apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Advisories affecting werkzeug 2.3.8
Werkzeug safe_join() allows Windows special device names
- Affected
- <3.1.9
- Fixed in
- 3.1.9
Werkzeug safe_join() allows Windows special device names
- Affected
- <3.1.6
- Fixed in
- 3.1.6
Werkzeug safe_join() allows Windows special device names with compound extensions
- Affected
- <3.1.5
- Fixed in
- 3.1.5
Werkzeug safe_join() allows Windows special device names
- Affected
- <3.1.4
- Fixed in
- 3.1.4
Werkzeug possible resource exhaustion when parsing file data in forms
- Affected
- >=2.0.0rc1 <3.0.6
- Fixed in
- 3.0.6
Werkzeug safe_join not safe on Windows
- Affected
- <3.0.6
- Fixed in
- 3.0.6
Werkzeug debugger vulnerable to remote execution when interacting with attacker controlled domain
- Affected
- <3.0.3
- Fixed in
- 3.0.3
Fixed within 2.3.x, affecting earlier releases
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
Every werkzeug 2.3.x release
Affected: 2.3.0 to 2.3.8. Latest werkzeug: 3.1.9.
| Version | Known advisories |
|---|---|
| werkzeug 2.3.8 | CVE-2026-102598, CVE-2026-27199, CVE-2026-21860, CVE-2025-66221, CVE-2024-49767, CVE-2024-49766, CVE-2024-34069 |
| werkzeug 2.3.7 | CVE-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.3.6 | CVE-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.3.5 | CVE-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.3.4 | CVE-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.3.3 | CVE-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.3.2 | CVE-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.3.1 | CVE-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.3.0 | CVE-2026-102598, CVE-2026-27199, CVE-2026-21860, CVE-2025-66221, CVE-2024-49767, CVE-2024-49766, CVE-2024-34069, CVE-2023-46136 |
Which of your client projects are still on werkzeug 2.3?
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.