PatchSiren

PatchSiren cyber security CVE debrief

CVE-2026-58189 Apache CVE debrief

Apache Traffic Server allows redirect-limit bypass when plugins reset the retry counter, enabling SSRF amplification. This issue affects Apache Traffic Server: from 8.0.0 through 8.1.9, from 9.0.0 through 9.2.14, from 10.0.0 through 10.1.3. Users are recommended to upgrade to version 9.2.15 or 10.1.4, which fix the issue. The vulnerability can lead to SSRF amplification attacks, which can have significant operational impacts. It is essential for operators, security teams, and vulnerability management teams to take immediate action to prevent these attacks. Affected deployments should be identified, and owners should be assigned for follow-up. Official advisories and CVE records should be reviewed to validate affected scope, severity, and vendor guidance.

Vendor
Apache
Product
Traffic Server
CVSS
HIGH 8.2
CISA KEV
Not listed in stored evidence
Original CVE published
2026-07-29
Original CVE updated
2026-08-03
Advisory published
2026-07-29
Advisory updated
2026-08-03

Who should care

Users of Apache Traffic Server versions 8.0.0 through 8.1.9, 9.0.0 through 9.2.14, and 10.0.0 through 10.1.3 should upgrade to version 9.2.15 or 10.1.4 to prevent redirect-limit bypass and SSRF amplification attacks. This includes operators, security teams, and vulnerability management teams responsible for maintaining and securing Apache Traffic Server deployments.

Technical summary

Apache Traffic Server allows redirect-limit bypass when plugins reset the retry counter, enabling SSRF amplification. This issue affects Apache Traffic Server: from 8.0.0 through 8.1.9, from 9.0.0 through 9.2.14, from 10.0.0 through 10.1.3. The vulnerability can be mitigated by upgrading to fixed versions 9.2.15 or 10.1.4. This issue has a high CVSS score of 8.2, indicating a high severity vulnerability. Defenders should confirm exposure, plan updates, and monitor for potential SSRF amplification attacks. Compensating controls should be reviewed for exposed systems while remediation is scheduled and verified.

Defensive priority

Upgrade to fixed versions 9.2.15 or 10.1.4 to prevent redirect-limit bypass and SSRF amplification attacks.

Recommended defensive actions

  • Upgrade to version 9.2.15 or 10.1.4
  • Review and apply vendor advisories
  • Monitor for potential SSRF amplification attacks
  • Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up.
  • Review the supplied official advisory or CVE record to validate affected scope, severity, and vendor guidance.
  • Plan vendor-supported updates or mitigations through normal change control where exposure is confirmed.
  • Check relevant monitoring, detection, and logs for exposed assets that need extra review.

Evidence notes

The CVE record and NVD detail provide information on the vulnerability, affected versions, and recommended upgrades. Evidence limits suggest verifying affected deployments exist and reviewing official advisories. Defenders should confirm exposure, plan updates, and monitor for potential SSRF amplification attacks. The NVD entry is currently Analyzed, and the CVE record was published on 2026-07-29T10:16:44.243Z. Additional verification tasks include reviewing compensating controls and checking relevant monitoring, detection, and logs for exposed assets.

Sources and references

Verified primary and authoritative sources

  • CVE-2026-58189 CVE Program record

    Publisher, destination, and source semantics verified

    URL: https://www.cve.org/CVERecord?id=CVE-2026-58189

    CVE Program - Official CVE Program record with source-provided CVE metadata.

  • CVE-2026-58189 NVD vulnerability detail

    Publisher, destination, and source semantics verified

    URL: https://nvd.nist.gov/vuln/detail/CVE-2026-58189

    NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.

Supplemental references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.