waitress vulnerabilities
Waitress WSGI server
- Registry
- PyPI
- Latest
- 3.0.2
- License
- ZPL 2.1
10 known advisories
The latest version, 3.0.2, is not affected by any of them. Projects on older versions may be.
pip install 'waitress>=3.0.2'Is your project on an affected waitress?
Look after several Python apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Security advisories for waitress
Waitress has request processing race condition in HTTP pipelining with invalid first request
- Affected
- >=2.0.0 <3.0.1
- Fixed in
- 3.0.1
Waitress vulnerable to DoS leading to high CPU usage/resource exhaustion
- Affected
- <3.0.1
- Fixed in
- 3.0.1
Uncaught Exception (due to a data race) leads to process termination in Waitress
- Affected
- >=2.1.0 <2.1.2
- Fixed in
- 2.1.2
HTTP Request Smuggling in waitress
- Affected
- <2.1.1
- Fixed in
- 2.1.1
Catastrophic backtracking in regex allows Denial of Service in Waitress
- Affected
- >=1.4.2 <1.4.3
- Fixed in
- 1.4.3
HTTP Request Smuggling in Waitress: Invalid whitespace characters in headers (Follow-up)
- Affected
- <1.4.2
- Fixed in
- 1.4.2
HTTP Request Smuggling: Invalid whitespace characters in headers in Waitress
- Affected
- <1.4.1
- Fixed in
- 1.4.1
HTTP Request Smuggling: Content-Length Sent Twice in Waitress
- Affected
- <1.4.0
- Fixed in
- 1.4.0
HTTP Request Smuggling: Invalid Transfer-Encoding in Waitress
- Affected
- <1.4.0
- Fixed in
- 1.4.0
HTTP Request Smuggling: LF vs CRLF handling in Waitress
- Affected
- <1.4.0
- Fixed in
- 1.4.0
Is your waitress version vulnerable?
Which of your client projects still run an old waitress?
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.