Is CVE-2026-58189 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-58189 being exploited in the wild.

How severe is CVE-2026-58189?

High severity, with a CVSS score of 7.5, published 29 July 2026.

Which products and versions are affected?

Apache Traffic Server 8.0.0 through 8.1.9, 9.0.0 through 9.2.14, 10.0.0 through 10.1.3.

Is there a fix for CVE-2026-58189?

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-58189 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2026-58189?

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.

CVE-2026-58189: Apache Traffic Server SSRF amplification via redirect-limit bypass

CVE-2026-58189 · Severity: high · CVSS 7.5 · Published 2026-07-29

Apache Traffic Server, a high-performance caching proxy used to manage web traffic, contains a vulnerability that allows attackers to bypass security limits on web redirects. By exploiting this flaw, an attacker could force the server to repeatedly request internal or external resources, potentially leading to a denial-of-service condition or unauthorized internal network scanning. This could disrupt service availability and impact the overall performance of the web infrastructure.

Technologies: Apache Traffic Server. Vendors: Apache.

Quick answers

Is CVE-2026-58189 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-58189 being exploited in the wild.
How severe is CVE-2026-58189?: High severity, with a CVSS score of 7.5, published 29 July 2026.
Which products and versions are affected?: Apache Traffic Server 8.0.0 through 8.1.9, 9.0.0 through 9.2.14, 10.0.0 through 10.1.3.
Is there a fix for CVE-2026-58189?: 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-58189 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2026-58189?: 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

A Server-Side Request Forgery (SSRF) amplification vulnerability exists in Apache Traffic Server due to an improper handling of the redirect limit. When specific plugins reset the retry counter, the server fails to enforce the configured maximum number of redirects. A remote, unauthenticated attacker can exploit this behavior to bypass redirect limits, potentially leading to resource exhaustion or internal network probing. The issue affects versions 8.x, 9.x, and 10.x, and is resolved in versions 9.2.15 and 10.1.4.

Affected products

Apache Traffic Server 8.0.0 through 8.1.9, 9.0.0 through 9.2.14, 10.0.0 through 10.1.3

Timeline

2026-07-29: disclosed
2026-07-29: advisory

References

https://lists.apache.org/thread/5prl9glcm9g2swnq9hqxvnokylm1gr6d

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.