CVE-2019-16789 is a high-severity (CVSS 8.2) CWE-444 vulnerability in waitress. A fix is available for waitress — see the affected versions and patch details below.
HTTP Request Smuggling in Waitress: Invalid whitespace characters in headers (Follow-up)
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
waitressReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.
Description
In Waitress through version 1.4.0, if a proxy server is used in front of waitress, an invalid request may be sent by an attacker that bypasses the front-end and is parsed differently by waitress leading to a potential for HTTP request smuggling. Specially crafted requests containing special whitespace characters in the Transfer-Encoding header would get parsed by Waitress as being a chunked request, but a front-end server would use the Content-Length instead as the Transfer-Encoding header is considered invalid due to containing invalid characters. If a front-end server does HTTP pipelining to a backend Waitress server this could lead to HTTP request splitting which may lead to potential cache poisoning or unexpected information disclosure. This issue is fixed in Waitress 1.4.1 through more strict HTTP field validation.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐍PyPI | waitress | all versions | 1.4.2pip install --upgrade 'waitress==1.4.2' |
Affected Products
waitressagendalessdebian linuxdebianfedorafedoraprojectcommunications cloud native core network function cloud native environmentoracleopenstackredhatDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for waitress, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update waitress to 1.4.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2019-16789 is resolved across your whole dependency graph.
Workarounds
Assume what was exposed is already known: rotate any credential, token or key that the affected component could return, restrict the endpoint to callers that genuinely need it, and strip sensitive fields from responses and error output at the boundary rather than relying on the client not to read them.
Fixing This On Your OS
If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.
All affected Red Hat products ship but do not use the flawed version of python-waitress. The impact for these products is therefore rated as having a security impact of Low. For Red Hat OpenStack Platform 13, because the flaw has a lower impact and the fix would require a substantial amount of development, no update…
| Product | Fixed in | Advisory |
|---|---|---|
| Red Hat OpenStack Platform 15.0 (Stein) | python-waitress-0:1.4.2-1.el8ost | RHSA-2020:0720 |
| Red Hat Quay 3 | quay/clair-rhel8:v3.4.0-25 | RHSA-2021:0420 |
Frequently Asked Questions
Is CVE-2019-16789 in your dependencies?
Find it across PyPI, including transitive dependencies.