Cyber Resilience

CVE-2025-65114

Apache Traffic Server 9.0.0 – 9.2.13

Published
02 April 2026
Modified
24 July 2026
Patch / advisory
CVSS Score v3.1 7.5
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
EPSS Score 0.0043 35th percentile
Risk Priority 57 floored blend · peak EPSS

Summary

CVE-2025-65114 is a high-severity HTTP Request/Response Smuggling (CWE-444) vulnerability in Apache Traffic Server. Its CVSS base score is 7.5 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked at the 35th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to SC-7 (Boundary Protection) and SI-10 (Information Input Validation) — see the control section below for these in your framework.

Deeper analysis AI-assisted summary

Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.

CVE-2025-65114 is a vulnerability in Apache Traffic Server that enables HTTP request smuggling when chunked messages are malformed. The issue affects Apache Traffic Server versions from 9.0.0 through 9.2.12 and from 10.0.0 through 10.1.1. It is classified under CWE-444 and carries a CVSS v3.1 base score of 7.5 (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N), highlighting its potential for network-based integrity violations.

Unauthenticated remote attackers with network access to a vulnerable Apache Traffic Server instance can exploit this flaw with low complexity and no user interaction required. By sending specially crafted malformed chunked requests, attackers can perform HTTP request smuggling, achieving high integrity impact such as interfering with request processing or routing.

The Apache advisory, detailed in the mailing list thread at https://lists.apache.org/thread/2s11roxlv1j8ph6q52rqo1klvl01n14q, recommends upgrading to remedied versions 9.2.13 or 10.1.2 to mitigate the vulnerability.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

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.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2024-35161Same product: Apache Traffic Server
CVE-2024-53868Same product: Apache Traffic Server
CVE-2026-24033Same product: Apache Traffic Server
CVE-2026-58150Same product: Apache Traffic Server
CVE-2026-58155Same product: Apache Traffic Server
CVE-2023-38522Same product: Apache Traffic Server
CVE-2026-57834Same product: Apache Traffic Server
CVE-2023-33934Same product: Apache Traffic Server
CVE-2026-58153Same product: Apache Traffic Server
CVE-2026-58189Same product: Apache Traffic Server

Affected Assets

apache
traffic server
9.0.0 — 9.2.13 · 10.0.0 — 10.1.2

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

Detect
Catch it (NIST detect / respond)

Harden
Shrink the surface (DISA STIG)

Validate
Prove the fix (OWASP ASVS)
  • V4.1.3
  • V4.2.4
  • V1.5.3
  • V4.1.1

Mitigating Controls (NIST 800-53 r5) AI

Boundary protection at external interfaces can enforce consistent HTTP request/response parsing rules between intermediaries and endpoints.

Validating HTTP inputs at the intermediary prevents malformed messages from being interpreted inconsistently downstream.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-01 mostly match
prevents

Configuration management can enforce uniform HTTP parsing rules across intermediaries, directly mitigating inconsistent interpretation.

DE.CM-01 partial match
prevents

Network monitoring can detect smuggling attempts via anomalous HTTP traffic or logs, while eliminating the inconsistency directly aids detection of such events.

PR.IR-01 partial match
prevents

Network protections can enforce consistent HTTP proxy/firewall behavior to block smuggling, and removing the weakness helps prevent unauthorized access via request smuggling.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

finds

Security testing can detect HTTP request smuggling vulnerabilities in intermediary components.

degrades

Network security controls can enforce consistent HTTP parsing and proxy behavior that mitigates request smuggling.

degrades

Secure network services include hardening proxies and gateways against inconsistent HTTP interpretation.

prevents

Secure SDLC practices require threat modeling and testing for HTTP parsing inconsistencies in intermediaries.

prevents

Application security requirements can mandate strict HTTP message validation and canonicalization.

prevents

Secure architecture principles include consistent protocol handling and defense-in-depth for proxies.

References