PYSEC-2022-203 in werkzeug
Published 25 May 2022 · Updated 8 Nov 2023
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
Affected package
- Affected
- <2.1.1
- Fixed in
- 2.1.1
pip install 'werkzeug>=2.1.1'Details
DISPUTED Improper parsing of HTTP requests in Pallets Werkzeug v2.1.0 and below allows attackers to perform HTTP Request Smuggling using a crafted HTTP request with multiple requests included inside the body. NOTE: the vendor's position is that this behavior can only occur in unsupported configurations involving development mode and an HTTP server from outside the Werkzeug project.
Is PYSEC-2022-203 in any of your client repos?
Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected werkzeug, and gives you the command that fixes it.
More advisories for werkzeug
- MediumCVE-2026-102598Werkzeug safe_join() allows Windows special device names · 5 Oct 2026
- MediumCVE-2026-27199 Werkzeug safe_join() allows Windows special device names · 19 Feb 2026
- MediumCVE-2026-21860 Werkzeug safe_join() allows Windows special device names with compound extensions · 8 Jan 2026
- MediumCVE-2025-66221Werkzeug safe_join() allows Windows special device names · 2 Dec 2025
- MediumCVE-2024-49767Werkzeug possible resource exhaustion when parsing file data in forms · 25 Oct 2024
- MediumCVE-2024-49766Werkzeug safe_join not safe on Windows · 25 Oct 2024
References
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.