CVE-2025-31699criticalCWE-444

CVE-2025-31699: critical vulnerability in Apache Traffic Server

Apache Traffic Server: Origin connection still owed a request body is reused, enabling request smuggling

Published · Updated

Follow this CVE+ Monitor Apache Traffic Server+ Monitor trafficserver

E-mail alert when it lands in KEV, gets a public PoC or its score goes up.

28Vexday Risk Score

No sign of exploitation. No public exploitation artifact known so far.

ssvc Trackcvss 9.1epss 0.3%
Apache Traffic Server can return an origin connection to the shared pool while the origin is still waiting on a request body the client declared but never fully sent, including when the client used Expect: 100-continue. The origin then reads a later request on that connection as leftover body data, which lets an attacker smuggle requests past ATS access controls, disrupt other users' requests, or poison the cache. 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:L/VI:H/VA:L/SC:H/SI:H/SA:L
Affected products
Apache Software Foundation · Apache Traffic Server
Related 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%