Skip to content
fr Sign in
9.3 Critical

CVE-2026-111816 Apache Traffic Server forwarded a malformed 302 response that should have been rejected as a parse error, because the…

Description

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.

Affected products and versions

Product Affected versions Fixed in
Apache Traffic Server 10.2.0 No fix stated
Apache Traffic Server 10.0 10.0.0 → 10.1.4 No fix stated
Apache Traffic Server 9.0 9.0.0 → 9.2.15 No fix stated
Apache Traffic Server 8.0 8.0.0 → 8.1.11 No fix stated

References

Timeline

  1. Published
  2. Last modified

Other CVEs of Apache Traffic Server

The 111 CVEs of Apache Traffic Server →
CVE-2026-112381 Apache Traffic Server can crash with a null pointer dereference when a client POST request is torn down via half-close… 5.9 Medium CVE-2026-111817 Apache Traffic Server can stall a chunked transfer that it passes through with its trailers removed… 5.3 Medium CVE-2026-111812 Apache Traffic Server's origin_server_auth plugin lets a client force signing of attacker-chosen AWS request headers… 10.0 Critical CVE-2026-111811 Apache Traffic Server's experimental tsmemcache plugin allows unauthenticated network read, write, and deletion of the… 9.0 Critical
Track this CVE