https://vulnerability.circl.lu/rss/recent/all/10 Most recent entries from all 2026-09-29T02:33:02.875084+00:00 Vulnerability-Lookup info@circl.lu python-feedgen Contains only the most 10 recent entries. https://vulnerability.circl.lu/vuln/brew-backgroundremover-ghsa-m5ff-3wj3-8ph4 BREW-backgroundremover-GHSA-m5ff-3wj3-8ph4 — HTTP Request Smuggling: Invalid whitespace characters in headers in Waitress 2026-09-29T02:33:02.880821+00:00

Affected: Homebrew: backgroundremover

### Impact

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.

``` Content-Length: 10 Transfer-Encoding: [\x0b]chunked ```

For clarity:

``` 0x0b == vertical tab ```

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.

### Patches

Please upgrade to Waitress 1.4.1 which fixes this issue with stricter HTTP field validation.

Waitress 1.4.1 due to this change has become much more strict in what is allowed in header values, while the maintainers don't believe that these changes will cause any issues, it may cause failures with non-conformist reverse proxies or clients, and it is highly recommend that users validate the changes in their environment and make sure it won't cause any unacceptable failures.

### Workarounds

You may enable additional protections on front-end servers, those that follow RFC7230 correctly would drop the request with a 400 Bad Request.

Waitress will now correctly responds to the request with a 400 Bad Request, and will drop the connection…

 https://vulnerability.circl.lu/vuln/cve-2019-16789 CVE-2019-16789 — HTTP Request Smuggling in Waitress: Invalid whitespace characters in headers 2026-09-29T02:33:02.881024+00:00

Affected: Pylons Waitress

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.