Apache Traffic Server: Malformed chunked message body allows request smuggling

published 2026-04-02 7 mo ago modified 2026-07-24 3 mo ago also EUVD-2025-209190

cvss: 7.5; version 3.1, CNA
cisa kev: Not listed; not in CISA's catalog
epss: 0.4%; EPSS 0.4% chance of exploitation in 30 days, percentile 38%
public exploits: 0; none known

Apache Traffic Server allows request smuggling if chunked messages are malformed.

This issue affects Apache Traffic Server: from 9.0.0 through 9.2.12, from 10.0.0 through 10.1.1.

Users are recommended to upgrade to version 9.2.13 or 10.1.2, which fix the issue.

Patch / fix

fixed in 1 distros 1

apache traffic_server 9.2.13, 10.1.2

trafficserver Debian 12 9.2.5+ds-0+deb12u4

debian advisories DEBIAN-CVE-2025-65114

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2025-65114 updated 2026-06-28 cvss 7.5

Apache Traffic Server: Apache Traffic Server: Request smuggling due to malformed chunked messages

Red Hat All currently supported Red Hat products
not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation: none
Automatable: yes
Technical impact: partial
Assessed: 7 mo ago (2026-04-02)

Exploit prediction

0.45% chance of exploitation in the next 30 days, higher than 38% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by	version	score	vector
CISA ADP	3.1	7.5	CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
CNA	3.1	7.5	CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N

Affected products

Apache Software Foundation Apache Traffic Server

Classification

Weakness

CWE-444 Inconsistent Interpretation of HTTP Requests

References

lists.apache.org /thread/2s11roxlv1j8ph6q52rqo1klvl01n14q
vendor-advisory, mailing-list

Sources

CVE List CVE-2025-65114
NVD CVE-2025-65114

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

Summary