CVE-2025-55702: high-severity vulnerability in Apache Traffic Server
Apache Traffic Server: An unread Expect: 100-continue request body is framed as a new request
Published · Updated
E-mail alert when it lands in KEV, gets a public PoC or its score goes up.
21Vexday Risk Score
No sign of exploitation. No public exploitation artifact known so far.
ssvc Trackcvss 7epss 0.3%
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.
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:N/SC:H/SI:H/SA:N
Affected products
Apache Software Foundation · Apache Traffic ServerRelated CVEs — Apache Traffic Server
In the same product, most dangerous first.
CVE-2024-31309HIGHApache Traffic Server: HTTP/2 CONTINUATION frames can be utilized for DoS attackEPSS 94.6%CVE-2023-39456HIGHApache Traffic Server: Malformed http/2 frames can cause an abortEPSS 58.3%CVE-2018-1318—CVE-2018-1318EPSS 7.7%CVE-2018-8022—CVE-2018-8022EPSS 7.5%CVE-2018-8040—CVE-2018-8040EPSS 7.2%CVE-2018-8005—CVE-2018-8005EPSS 6.9%