dbcve.org
Traffic ServerApplication · Apache

CVE-2025-65114

HIGH · 7.5 CVSS v3.1 Published 2026-04-02
Fix available
A fix is available. Upgrade to 9.2.13 / 10.1.2 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Apache Traffic Server before versions 9.2.13 and 10.1.2 is vulnerable to HTTP request smuggling due to improper parsing of malformed chunked transfer-encoded messages. An attacker can send specially crafted requests with inconsistent Content-Length or Transfer-Encoding headers to cause the proxy to interpret requests differently than backend servers, potentially bypassing security controls, hijacking connections, or poisoning caches.

MitigationUpgrade Apache Traffic Server to version 9.2.13 or 10.1.2 to patch the request smuggling vulnerability. In production environments, test the upgrade thoroughly before deployment as Traffic Server sits in the critical request path.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Traffic ServerApplication
Affected:>= 9.0.0, < 9.2.13>= 10.0.0, < 10.1.2

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Apache Traffic Server installation
    Run 'traffic_server -V' or check package manager for ats/apache-traffic-server
    Affected if Apache Traffic Server is not installed or cannot be determined
  2. Determine installed version
    Execute 'traffic_server -V' to get the exact version number, or check the RPM/DEB package version
    Affected if Version is 9.0.0 through 9.2.12, or 10.0.0 through 10.1.1
  3. Verify proxy configuration
    Inspect the records.config or traffic server configuration for proxy settings; check if the server is configured as a forward or reverse proxy by looking for 'proxy.config.http.enable' or similar proxy-related directives
    Affected if Server is configured as a proxy handling backend connections
  4. Confirm chunked transfer encoding usage
    Review proxy.config.http.chunked_* settings in records.config or check if chunked transfer encoding is allowed/enabled in the proxy configuration
    Affected if Chunked transfer encoding is enabled for proxy connections

A user is affected if they are running Apache Traffic Server versions 9.0.0-9.2.12 or 10.0.0-10.1.1 configured as a proxy that handles chunked transfer-encoded HTTP requests.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 9.2.13 / 10.1.2 or later
Fixed in 9.2.1310.1.2
Interim mitigation

Upgrade Apache Traffic Server to version 9.2.13 or 10.1.2 to patch the request smuggling vulnerability. In production environments, test the upgrade thoroughly before deployment as Traffic Server sits in the critical request path.

Recommended fix High confidence

9.2.13 or 10.1.2

  1. 1. Identify the currently installed Apache Traffic Server version using: traffic_server -version or ats -version
  2. 2. If running version 9.0.0 through 9.2.12, upgrade to version 9.2.13
  3. 3. If running version 10.0.0 through 10.1.1, upgrade to version 10.1.2
  4. 4. Download the appropriate fixed version from the Apache Traffic Server downloads page: https://traffic.apache.org/download/
  5. 5. Follow the standard upgrade procedure for your operating system (package manager or compile from source)
  6. 6. Restart the Traffic Server service after upgrading
  7. 7. Verify the new version is running: traffic_server -version

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Traffic Server Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing6.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,220
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,552.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-65114 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-65114 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data