Skip to main content

Apache Traffic Server CVE-2026-58152

| EUVDEUVD-2026-50204 MEDIUM
Integer Overflow or Wraparound (CWE-190)
2026-07-29 apache GHSA-3mm3-f2hp-jpcj
6.9
CVSS 4.0 · Vendor: apache
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Send crafted HTTP/2 or HTTP/3 request
  2. Delivery
    Deliver malformed HPACK/XPACK integer-encoded header
  3. Exploit
    Trigger integer overflow in ATS decoder
  4. Execution
    Corrupt server heap memory
  5. Persist
    Crash Apache Traffic Server process
  6. Impact
    Deny service to downstream clients

Vulnerability Assessment

Weakness
CWE
ASVS 5.0
V15 - Secure Coding and Architecture Integer overflow checks
MITRE ATT&CK

1 technique across 1 tactic: Execution

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

Exploitation requires Apache Traffic Server to be running a vulnerable version (8.0.0-8.1.9, 9.0.0-9.2.14, or 10.0.0-10.1.3) with HTTP/2 or HTTP/3 (QUIC) protocol support enabled and accessible from the attacker's network position. The CVSS AC:H rating indicates that the attacker must craft a specific malformed integer sequence within HPACK/XPACK header encoding - a generic or randomly malformed request is unlikely to trigger the overflow. No authentication is required (PR:N), and no user interaction is needed (UI:N). Exploitation is limited to denial of service; the CVSS C:N/I:N metrics confirm no confidentiality or integrity impact is expected. Deployments that terminate HTTP/2 at an upstream load balancer or reverse proxy before reaching ATS may have reduced exposure if that intermediary validates or re-encodes HPACK headers.

Impact

The CVSS 3.1 base score of 5.9 (Medium) is consistent with the available signals. The AV:N metric confirms the attack surface is network-reachable without special positioning, but AC:H substantially reduces real-world risk by requiring the attacker to engineer a precisely malformed integer encoding in HPACK/XPACK headers - automated scanning tools are unlikely to trigger this reliably. PR:N means no credentials are needed, which broadens the potential attacker pool. The impact metrics C:N/I:N/A:H constrain the worst-case outcome to a service crash, with no data exfiltration or integrity compromise. This vulnerability is not listed in CISA KEV, no public proof-of-concept has been identified, and no EPSS data was available in the provided intelligence - all consistent with a moderate, not yet actively targeted issue. Notably, the advisory tags include 'Information Disclosure', which directly conflicts with the CVSS C:N rating; this tag appears to be erroneous, and the CVSS vector is treated as authoritative. The primary real-world risk is availability disruption to any service fronted by a vulnerable ATS instance, particularly relevant for CDN and reverse-proxy operators. Given the AC:H rating, this is a real but not urgent priority unless the deployment is exposed to untrusted HTTP/2 or HTTP/3 traffic at scale.

Exploit ScenarioDerived

An unauthenticated attacker sends a crafted HTTP/2 request containing a malformed HPACK header block in which an integer field is encoded to produce an overflow when decoded by Apache Traffic Server. The corrupted integer propagates into memory allocation or buffer indexing logic, corrupting the ATS process heap and causing a crash, taking down the proxy or cache service. No public exploit code has been identified at time of analysis, and the AC:H rating indicates successful triggering requires precise crafting of the integer encoding.

This Month Plan within 30 days. Why: MEDIUM severity (CVSS 4.0-6.9).
No patch listed yet 0.2% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Jul 29, 2026

Memory corruption in Apache Traffic Server during HPACK/XPACK header decoding exposes affected deployments to denial of service. Versions spanning the 8.x, 9.x, and 10.x release lines are affected, with unauthenticated remote attackers able to craft malformed compressed headers that trigger an integer overflow (CWE-190), corrupting server memory. The CVSS vector (AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H) scores 5.9 Medium, reflecting that while no authentication is required, elevated attack complexity limits opportunistic mass exploitation; no public exploit has been identified at time of analysis and this vulnerability is not listed in CISA KEV.

RemediationAI

Upgrade Apache Traffic Server to version 9.2.15 or 10.1.4, both of which are confirmed by the vendor as fixing this issue per the advisory at https://lists.apache.org/thread/5prl9glcm9g2swnq9hqxvnokylm1gr6d. The 8.x branch has no fix version listed; operators on 8.x should migrate to a supported release branch immediately. If an immediate upgrade is not feasible, consider restricting HTTP/2 and HTTP/3 (QUIC) traffic to trusted upstream sources via network ACLs or an edge load balancer that validates HPACK/XPACK encoding before forwarding - note this adds latency and may not be complete protection. Disabling HTTP/2 and HTTP/3 support in the ATS configuration entirely eliminates the attack surface but degrades protocol performance and compatibility with modern clients. No patch is available for the 8.x branch.

Affected VersionsENISA

Apache Traffic Server 10.0.0 ≤10.1.3
Apache Traffic Server 8.0.0 ≤8.1.9
Apache Traffic Server 9.0.0 ≤9.2.14

Affected Packages

euvd apache_traffic_server no fix

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

Apache Traffic Server (ATS) is a high-performance, open-source HTTP proxy and caching server widely used in CDN and reverse-proxy deployments. HPACK is the header compression algorithm mandated by HTTP/2 (RFC 7541), and XPACK is its counterpart for HTTP/3 over QUIC. Both formats encode header field lengths and indices as variable-length integers; the root cause is CWE-190 (Integer Overflow or Wraparound) - when ATS decodes these integers, it performs arithmetic that can exceed the expected integer bounds, producing a corrupted value used for memory operations. The affected CPE is cpe:2.3:a:apache_software_foundation:apache_traffic_server across the 8.0.0-8.1.9, 9.0.0-9.2.14, and 10.0.0-10.1.3 ranges. This class of bug in protocol header parsers is well-understood and historically leads to heap corruption, typically manifesting as a crash rather than arbitrary code execution when integer semantics do not directly control a write primitive.

Know when Apache Traffic Server gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (apache) PRIMARY 6.9 MEDIUM
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:L/SA:N
vuln.today AI 5.9 MEDIUM

Network-reachable HPACK/XPACK parser requires precisely crafted integer encoding (AC:H); no authentication needed; impact is crash-only with no confidentiality or integrity exposure.

3.1 AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H
4.0 AV:N/AC:H/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N

Primary rating from Vendor (apache).

CVSS VectorVendor: apache

Attack Vector
Network
Attack Complexity
Low
Attack Requirements
None
Privileges Required
None
User Interaction
None
Vulnerable system: Confidentiality
None
Vulnerable system: Integrity
Low
Vulnerable system: Availability
None
Subsequent system: Confidentiality
None
Subsequent system: Integrity
Low
Subsequent system: Availability
None

Lifecycle Timeline

2
CVSS changed
Jul 29, 2026 - 09:22 NVD
5.9 (MEDIUM) 6.9 (MEDIUM)
CVE Published
Jul 29, 2026 - 08:16 cve.org
MEDIUM 5.9

DescriptionCVE.org

Apache Traffic Server mishandles integers while decoding HPACK/XPACK headers, corrupting memory.

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.

Threat Intelligence Overview

EPSS Score
0.2%
Top 86% exploitable
Prevalence
Medium
enterprise HTTP/2 proxy used in CDN and large-scale web deployments
Data Quality
6 sources
Confidence: High

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity MEDIUM
CISA KEV No
Public POC No
EPSS 0.2%
Patch available No
Active threat No
Deciding rule
MEDIUM severity (CVSS 4.0-6.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Scheduled
Exploitation
None
System Exposure· derived
Open
Automatable
No
Human Impact· derived
Medium
Technical Impact
Partial

Priority Score

34
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +34
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Integer overflow occurs when an arithmetic operation produces a result that exceeds the maximum value a given integer type can store.

Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.

CVE-2026-111813 CRITICAL
10.0 Oct 21

Apache Traffic Server versions 8.0.1 through 8.1.11, 9.0.0 through 9.2.15, 10.0.0 through 10.1.4, and 10.2.0 ship an exp

CVE-2026-58161 CRITICAL
9.2 Jul 29

Remote denial of service in Apache Traffic Server (8.0.0-8.1.9, 9.0.0-9.2.14, 10.0.0-10.1.3) allows unauthenticated atta

CVE-2026-58154 CRITICAL
9.2 Jul 29

Out-of-bounds write and integer overflow in Apache Traffic Server's MIME and HTTP header parsing lets remote attackers c

CVE-2026-58155 CRITICAL
9.2 Jul 29

Request smuggling and policy bypass in Apache Traffic Server (branches 8.0.0-8.1.9, 9.0.0-9.2.14, and 10.0.0-10.1.3) ari

CVE-2026-111816 CRITICAL
9.2 Oct 21

Response-framing desync in Apache Traffic Server (8.0.0 through 8.1.11, 9.0.0 through 9.2.15, 10.0.0 through 10.1.4, and

CVE-2025-31699 CRITICAL
9.1 Oct 21

Request smuggling in Apache Traffic Server 8.0.0 through 8.1.11, 9.0.0 through 9.2.15, 10.0.0 through 10.1.4, and 10.2.0

CVE-2026-111804 HIGH
8.8 Oct 21

Unauthenticated remote attackers can drive HTTP transactions to completion against Apache Traffic Server instances that

CVE-2026-58151 HIGH
8.7 Jul 29

Denial of service in Apache Traffic Server 8.0.0-8.1.9, 9.0.0-9.2.14, and 10.0.0-10.1.3 lets remote unauthenticated atta

CVE-2026-111810 HIGH
8.7 Oct 21

Apache Traffic Server 9.2.15, 10.1.4, and 10.2.0 can be driven into a denial-of-service condition through log amplificat

CVE-2026-58188 HIGH
8.4 Jul 29

Out-of-bounds write and limit-bypass flaws in several experimental plugins shipped with Apache Traffic Server (8.0.0-8.1

CVE-2026-58162 HIGH
8.4 Jul 29

Improper certificate generation in the Apache Traffic Server certifier plugin lets remote attackers dictate the contents

CVE-2026-58164 HIGH
8.3 Jul 29

Memory corruption in Apache Traffic Server's remap configuration handling lets remote attackers trigger a use-after-free

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy