PyPI: pheonix-waitress

CVE-2019-16785

Safety vulnerability ID: SFTY-20191220-27176

Safety legacy ID: pyup.io-49025

Pheonix-waitress 1.4.0 includes a fix for CVE-2019-16785: Waitress through version 1.3.1 implemented a "MAY" part of the RFC7230 which states: "Although the line terminator for the start-line and header fields is the sequence CRLF, a recipient MAY recognize a single LF as a line terminator and ignore any preceding CR." Unfortunately if a front-end server does not parse header fields with an LF the same way as it does those with a CRLF it can lead to the front-end and the back-end server parsing the same HTTP message in two different ways. This can lead to a potential for HTTP request smuggling/splitting whereby Waitress may see two requests while the front-end server only sees a single HTTP message. https://github.com/Pylons/waitress/security/advisories/GHSA-pg36-wpm5-g57p

Created at: Jul 5, 2026Updated at: Jul 5, 2026

Overview

HTTP Request Smuggling: LF vs CRLF handling in Waitress

Advisory

Pheonix-waitress 1.4.0 includes a fix for CVE-2019-16785: Waitress through version 1.3.1 implemented a "MAY" part of the RFC7230 which states: "Although the line terminator for the start-line and header fields is the sequence CRLF, a recipient MAY recognize a single LF as a line terminator and ignore any preceding CR." Unfortunately if a front-end server does not parse header fields with an LF the same way as it does those with a CRLF it can lead to the front-end and the back-end server parsing the same HTTP message in two different ways. This can lead to a potential for HTTP request smuggling/splitting whereby Waitress may see two requests while the front-end server only sees a single HTTP message. https://github.com/Pylons/waitress/security/advisories/GHSA-pg36-wpm5-g57p

Affected Package

Affecting pheonix-waitress package, versions<1.4.0

Also affects

---

How to Fix

Upgradepheonix-waitressto2.1.1or higher.

Mitigation and Workarounds

---

Vulnerable Functions

Functions linked to known vulnerabilities.

Vulnerable function data is available for Enterprise customers

Book a call with us to see Safety in action.

Safety

Verified by Safety

Our Cybersecurity Intelligence Team reviewed this vulnerability. We combine public data with our own research to find issues not yet reported to public sources.

Learn more