CVE-2026-111816criticalCWE-444

CVE-2026-111816: critical vulnerability in Apache Traffic Server

Apache Traffic Server: A malformed 302 response bypasses parse-error rejection through the Transfer-Encoding: chunked carve-out

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.2epss 0.3%
Apache Traffic Server forwarded a malformed 302 response that should have been rejected as a parse error, because the Transfer-Encoding: chunked carve-out bypassed the rejection path. A response that two peers can read differently is then stored and served, allowing cache poisoning and response-framing desync. 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:N/PR:N/UI:N/VC:N/VI:H/VA:N/SC:L/SI:H/SA:N
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.6%CVE-2018-8022—CVE-2018-8022EPSS 7.4%CVE-2018-8040—CVE-2018-8040EPSS 7.2%CVE-2018-8005—CVE-2018-8005EPSS 6.8%