Skip to content
Networks

CVE-2026-58158

8.2
High
EPSS 0.34%Patch availableJul 29, 2026

Stack-based buffer overflow in Apache Traffic Server PROXY parsing enabling RCE/DoS.

common questions

Is CVE-2026-58158 being exploited?

Not confirmed. CVE-2026-58158 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.34% probability of exploitation in the next 30 days.

How severe is CVE-2026-58158?

CVE-2026-58158 is rated High with a CVSS score of 8.2. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-58158?

Yes. A fix has been recorded for CVE-2026-58158. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-58158 affect?

CVE-2026-58158 affects Apache Traffic Server 8.0.0 - 8.1.9, Apache Traffic Server 9.0.0 - 9.2.14, Apache Traffic Server 10.0.0 - 10.1.3, Services accepting PROXY protocol input. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-58158?

Upgrade to 9.2.15 or 10.1.4; block/validate PROXY inputs until patched.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
Apache Traffic Server 8.0.0 - 8.1.9Apache Traffic Server 9.0.0 - 9.2.14Apache Traffic Server 10.0.0 - 10.1.3Services accepting PROXY protocol input
impact

Crafted PROXY protocol input can trigger a stack overflow, enabling remote code execution or crash (denial of service).

action required

Immediate action required

affected versions
Apache Software Foundation Apache Traffic Server
  • affected>= 8.0.0 and <= 8.1.9
  • affected>= 9.0.0 and <= 9.2.14
  • affected>= 10.0.0 and <= 10.1.3

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free