External risk intelligence

Apache Traffic Server Request Smuggling and Cache Poisoning Vulnerability

CVE advisorySeverity: CRITICAL (CVSS 9.1)

CVE-2025-31699

Apache Traffic Server is a high-performance web proxy and caching server designed to function as an internet-facing gateway or edge service. By definition, its primary role is to handle incoming public web traffic and requests at the network edge, making this vulnerability accessible to the public internet in its normal, intended deployment pattern.

Halo Surface Signal: 5 out of 5 — more likely to be public-facing.

External exposure likelihood

Horizon Alert

Summary of the vulnerability and why it matters

This advisory concerns a vulnerability in Apache Traffic Server, a web proxy and caching system. The issue allows an attacker to manipulate requests, potentially bypassing access controls, disrupting other users, or compromising cached information by exploiting how the server handles incomplete client requests.

  • Attackers can bypass security controls and disrupt services.
  • Crucial for protecting edge services and cached content.
  • Verify relevance and exposure of this web traffic tool.

Attack Path

How an attacker could exploit the issue

An attacker can exploit this vulnerability by sending incomplete request bodies to Apache Traffic Server, specifically when using the "Expect: 100-continue" header. This causes the server to mishandle the connection, allowing the attacker to insert malicious requests that bypass security controls, disrupt other users, or corrupt cached data.

  • Attackers can reach the vulnerable component over the network.
  • Incomplete request bodies trigger the vulnerability.
  • Risks include request smuggling and cache poisoning.

Live Threat

Current exploitation, exposure, and threat context

Apache Traffic Server, when improperly handling incomplete client request bodies, could allow an attacker to bypass access controls, disrupt service for other users, or poison the cache. This occurs when the server prematurely returns an origin connection to its pool while still expecting data from a client, leading to the next request on that connection being misinterpreted.

  • Bypass access controls and poison cache.
  • Attackers can manipulate incomplete requests.
  • Disrupt service and compromise cache integrity.

Operational Fix

Recommended remediation, mitigation, and detection steps

Apache Traffic Server (ATS) administrators and platform owners are responsible for managing this critical vulnerability. The initial step is to locate all ATS deployments, determine their exposure to external networks, and assess their business criticality. This will inform prioritization for remediation, involving coordination with infrastructure, network, and security teams.

  • Own the ATS inventory and exposure.
  • Verify external reachability and criticality.
  • Plan and execute remediation.

Supplementary metadata

Validate whether this threat affects your internet-facing exposure.

Halo Threat Intelligence helps prioritize remediation with Halo Surface Signal and H/A/L/O context. Start exposure validation with a free external attack surface trial.

Frequently asked questions

What is Apache Traffic Server?

Apache Traffic Server is a high-performance, open-source web proxy and caching server. It acts as an intermediary for web traffic, sitting between clients and origin servers to accelerate content delivery, manage load balancing, and serve as an edge gateway for complex web applications.

What does CVE-2025-31699 mean by request smuggling?

This vulnerability is classified as CWE-444, or HTTP Request Smuggling. It occurs when a server misinterprets the boundaries between two different HTTP requests sent over the same connection. Because the server incorrectly reuses a connection while it still expects data from a previous request, it may mistake subsequent legitimate traffic for part of the original, incomplete request, leading to security bypasses or cache corruption.

How does an attacker trigger this vulnerability?

An attacker triggers this flaw by initiating a request that promises a body—often using the 'Expect: 100-continue' header—but fails to send that body completely. The vulnerability is not triggered by standard, fully formed requests, but specifically by these deliberately incomplete or stalled interactions that trick the server into incorrectly managing its connection pool.

Is my Apache Traffic Server instance at risk?

According to Halo Surface Signal, this vulnerability is particularly relevant because Apache Traffic Server is typically deployed as an internet-facing gateway. If your instance is configured to handle public web traffic at the network edge, it is directly exposed to these malicious, incomplete requests, making it a higher priority for review than internal-only services.

What should I do to secure my environment?

First, identify all instances of Apache Traffic Server within your infrastructure and confirm their network exposure. Once your inventory is mapped, prioritize upgrading your installations to the patched versions—9.2.16, 10.1.5, or 10.2.1—to resolve the underlying connection handling logic that permits this manipulation.

References