Live › vulnerability › CVE-2025-55702
Go to dashboardApache Traffic Server parses an unread POST body left on a client connection as a new request when the origin answers early to an Expect: 100-continue request. An attacker behind a front-end proxy that shares connections with Traffic Server can smuggle requests past the front end and desynchronize responses for other users.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-23 21:57 UTC. All times on this page are UTC.
No product ranges from the sources yet.
Check the installed Traffic Server version (for example with traffic_server -V) and see whether it falls in 8.0.0-8.1.11, 9.0.0-9.2.15, 10.0.0-10.1.4, or 10.2.0.
Upgrade to 9.2.16, 10.1.5, or 10.2.1, per the advisory.
Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
When a client sends a POST with Expect: 100-continue and the origin answers before reading the body, Apache Traffic Server parses the unread body left on the client connection as the next request. An attacker behind a front-end proxy that shares connections to Traffic Server can use this to smuggle requests past the front end and desynchronize responses for other users.
This issue affects Apache Traffic Server: from 8.0.0 through 8.1.11, from 9.0.0 through 9.2.15, from 10.0.0 through 10.1.4, 10.2.0.
Users are recommended to upgrade to version 9.2.16, 10.1.5, or 10.2.1, which fix the issue.
This page as .md · .json · in your agent: get_signal("CVE-2025-55702")
NVD data is provided by NIST and is public domain · EPSS scores by FIRST, used with attribution. Posts quoted belong to their authors.