Apache Traffic Server: Inconsistent Interpretation of HTTP Requests
CVE-2025-65114 is a high-severity inconsistent interpretation of HTTP requests vulnerability in Apache Traffic Server from Apache, with a CVSS 3.1 base score of 7.5 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, without any action from a user. Affected Apache Traffic Server versions: 9.0.0 through 9.2.12; 10.0.0 through 10.1.1. The record does not name a fixed version, so check the vendor advisory. There is no confirmed exploitation so far. EPSS estimates a 0.45% chance of exploitation within 30 days, which is low compared with other CVEs.
High severity with no evidence of exploitation so far.
What to do
- Update Traffic Server to 9.2.13 or 10.1.2, whichever matches your release line, or a later version.
- Read the advisory on lists.apache.org for workarounds and exact fixed builds.
- Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Apache | Apache Traffic Server | 9.0.0 through 9.2.12; 10.0.0 through 10.1.1 | Not stated |
| Apache | Traffic Server | 9.0.0 up to, but not including, 9.2.13; 10.0.0 up to, but not including, 10.1.2 | 9.2.13, 10.1.2 |
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- NetworkCan be exploited remotely over a network, including the internet.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- NoneNo account or login is needed.
- User interaction
- NoneNo action by a victim is required.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- NoneNo data is disclosed.
- Integrity
- HighData or code can be modified at will.
- Availability
- NoneAvailability is not affected.
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N. Scored by CISA (ADP).
Official description
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.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Inconsistent Interpretation of HTTP Requests
The product acts as an intermediary HTTP agent (such as a proxy or firewall) in the data flow between two entities such as a client and server, but it does not interpret malformed HTTP requests or responses in ways that are consistent with how the messages will be processed by those entities that are at the ultimate destination.
How developers prevent this class of flaw
- Use a web server that employs a strict HTTP parsing procedure, such as Apache.
- Terminate the client session after each request.
More Inconsistent Interpretation of HTTP Requests vulnerabilities (CWE-444)
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: yes, technical impact: partial).
- Record last changed materially (score, affected products, status or references).
References
Advisories
Other vulnerabilities in Apache Traffic Server
- 10.0 Critical severity
- 10.0 Critical severity
- 10.0 Critical severity
- 9.0 Critical severity
- 7.5 High severity
- 9.3 Critical severity
Recent Inconsistent Interpretation of HTTP Requests vulnerabilities
- 7.5 High severity
- 9.1 Critical severity
- 9.1 Critical severity
- 9.1 Critical severity
- 9.4 Critical severity
- 9.8 Critical severity
Spotted an error? Tell us.