Skip to content
VulniPulse
Advisory severityCritical9.2Apache Software Foundation Updated

Critical [CVE-2026-111816] 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

This critical-severity Apache Software Foundation advisory covers CVE-2026-111816 affecting Apache Traffic Server.

Aggregated and source-linked by VulniPulse. Data sources, validation and limitations.

CVE-2026-111816 Source published Source updated

VulniPulse record published Record updated

CVE-2026-111816
Affected products & platforms
Apache Software FoundationInfra & Gateways
Open source advisory

Android app · Google Play

Monitor future Apache Software Foundation CVEs from your phone.

Choose a whole vendor or a precise platform, then receive matching security advisories by phone notification, email, or both. Coverage follows 34 official vendor sources and 160+ reviewed platform categories.

Matching phone alertsOptional email delivery

Summary

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 versions
  • 8.0.0 through 8.1.11
  • 9.0.0 through 9.2.15
  • 10.0.0 through 10.1.4

Official advisory · high-confidence parse· fetched 12 hours ago·verify at source

Fixed versions
  • 9.2.16
  • 10.1.5
  • 10.2.1

Official advisory · high-confidence parse· fetched 12 hours ago·verify at source

Mitigation checklist

Recommended fix / mitigation
  • Users are recommended to upgrade to version 9.2.16, 10.1.5, or 10.2.1, which fix the issue.

Official advisory · high-confidence parse· fetched 12 hours ago·verify at source

Discussion(0)

No comments yet. Share field notes, upgrade gotchas, or questions — verify against the vendor advisory before acting on community advice.

Sign in to join the discussion.