Quick answers
- Is CVE-2026-58150 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-58150 being exploited in the wild.
- How severe is CVE-2026-58150?
- Critical severity, with a CVSS score of 10, published 29 July 2026.
- Which products and versions are affected?
- Apache Traffic Server 8.0.0 - 8.1.9, 9.0.0 - 9.2.14, 10.0.0 - 10.1.3.
- Is there a fix for CVE-2026-58150?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-58150 attacked?
- It is attacked over the network, in a hosted service.
- Am I affected by CVE-2026-58150?
- Check whether you run Apache Traffic Server at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
Apache Traffic Server (ATS) is vulnerable to HTTP request smuggling due to the improper handling of the 'Transfer-Encoding' header in HTTP/2 requests. While HTTP/2 uses a built-in framing mechanism for body length, ATS fails to reject requests containing the legacy Transfer-Encoding header. When these requests are downgraded to HTTP/1.1 for backend communication, an attacker can manipulate the request boundaries to 'smuggle' a second, hidden request. This can lead to cache poisoning, security filter bypass, or unauthorized access to backend resources. The issue is fixed in versions 9.2.15 and 10.1.4.
Affected products
- Apache Traffic Server 8.0.0 - 8.1.9, 9.0.0 - 9.2.14, 10.0.0 - 10.1.3
Timeline
- 2026-07-29: advisory: Initial advisory published by Apache and NVD.