Apache Traffic Server up to 8.1.9/9.2.14/10.1.3 allocation of resources

Summaryinfo

A vulnerability labeled as critical has been found in Apache Traffic Server up to 8.1.9/9.2.14/10.1.3. This affects an unknown part. Executing a manipulation can lead to allocation of resources. This vulnerability is registered as CVE-2026-65324. It is possible to launch the attack remotely. No exploit is available.

Detailsinfo

A vulnerability was found in Apache Traffic Server up to 8.1.9/9.2.14/10.1.3. It has been declared as critical. This vulnerability affects an unknown part. The manipulation with an unknown input leads to a allocation of resources vulnerability. The CWE definition for the vulnerability is CWE-770. The product allocates a reusable resource or group of resources on behalf of an actor without imposing any restrictions on the size or number of resources that can be allocated, in violation of the intended security policy for that actor. As an impact it is known to affect availability. CVE summarizes:

Apache Traffic Server drops the per-stream buffer cap when dechunking HTTP/2 or HTTP/3 responses, letting a slow client exhaust server 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.

The advisory is shared for download at lists.apache.org. This vulnerability was named CVE-2026-65324 since 07/21/2026. The exploitation appears to be easy. The attack can be initiated remotely. No form of authentication is required for a successful exploitation. There are neither technical details nor an exploit publicly available. The current price for an exploit might be approx. USD $0-$5k (estimation calculated on 07/29/2026). The MITRE ATT&CK project declares the attack technique as T1499.

Upgrading to version 9.2.15 or 10.1.4 eliminates this vulnerability.

The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2026-50206). Once again VulDB remains the best source for vulnerability data.

Productinfo

Vendor

• Apache

Name

• Traffic Server

Version

• 8.1.0
• 8.1.1
• 8.1.2
• 8.1.3
• 8.1.4
• 8.1.5
• 8.1.6
• 8.1.7
• 8.1.8
• 8.1.9
• 9.2.0
• 9.2.1
• 9.2.2
• 9.2.3
• 9.2.4
• 9.2.5
• 9.2.6
• 9.2.7
• 9.2.8
• 9.2.9
• 9.2.10
• 9.2.11
• 9.2.12
• 9.2.13
• 9.2.14
• 10.1.0
• 10.1.1
• 10.1.2
• 10.1.3

License

• open-source

Website

• Vendor: https://www.apache.org/

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Once again VulDB remains the best source for vulnerability data.

Discussion