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.
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
Security advisories for werkzeug
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
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
Incorrect parsing of nameless cookies leads to __Host- cookies bypass
- Affected
- <2.2.3
- Fixed in
- 2.2.3
High resource usage when parsing multipart form data with many fields
- Affected
- <2.2.3
- Fixed in
- 2.2.3
No summary published
- Affected
- <2.1.1
- Fixed in
- 2.1.1
Pallets Werkzeug vulnerable to Path Traversal
- Affected
- <0.15.5
- Fixed in
- 0.15.5
Pallets Werkzeug cross-site scripting vulnerability
- Affected
- <0.11.11
- Fixed in
- 0.11.11
Open Redirect in werkzeug
- Affected
- <0.11.6
- Fixed in
- 0.11.6
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.