Apache Traffic Server: Abusive HTTP/2 framing can exhaust resources and crash the server

Why this deserves its current priority

CVSS is 8.7. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Affected scope and exposure questions

The current feed maps Apache Software Foundation/Apache Traffic Server (generic). Check affected ranges and fixed versions before updating.

Recommended response

1. 1Check inventory. Check lockfiles and deployed manifests for Apache Software Foundation/Apache Traffic Server.
2. 2Review the reported fix. Monitor this advisory for an available fix and review any installs of the affected package.

Evidence timeline and material changes

1. Published upstream

   Jul 29, 2026

   Evidence: source:cvelist:source_dates:source-dates:record

2. Source modified

   Oct 1, 2026

   Evidence: source:cvelist:source_dates:source-dates:record

3. First seen by HOL

   Aug 3, 2026

Sources and claim methodology

• Source referencelists.apache.org

Related CVEs

• jackson-dataformats-binary: CBOR parser does not enforce StreamReadConstraints.maxNameLength, enabling memory-exhaustion denial of serviceAlso CWE-400
• jackson-dataformats-binary: Smile parser does not enforce StreamReadConstraints.maxNameLength, enabling memory-exhaustion denial of serviceAlso CWE-400
• Zod 4.6.5 Uncontrolled Resource Consumption via Array ValidationSame generic ecosystem
• HCL BigFix Service Management is affected by multiple security vulnerabilities.Same generic ecosystem
• Prime Mover < 2.2.1 Zip Slip Path Traversal File WriteSame generic ecosystem
• Prime Mover < 2.2.1 Path Traversal via wprime-config.jsonSame generic ecosystem