Quick answers
- Is CVE-2025-31699 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2025-31699 being exploited in the wild.
- How severe is CVE-2025-31699?
- High severity, with a CVSS score of 8.9, published 21 October 2026.
- Which products and versions are affected?
- Apache Traffic Server 8.0.0 through 8.1.11, 9.0.0 through 9.2.15, 10.0.0 through 10.1.4, 10.2.0.
- Is there a fix for CVE-2025-31699?
- Yes: fixed in Traffic Server 9.2.16, 10.1.5, or 10.2.1. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2025-31699 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2025-31699?
- Check whether you run Apache Traffic Server at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: Traffic Server 9.2.16, 10.1.5, or 10.2.1
Technical details
The vulnerability is an HTTP request smuggling issue where Traffic Server returns an origin connection to the shared pool prematurely while the origin is still waiting on a declared but incomplete request body. When the client uses Expect: 100-continue or sends incomplete body data, the connection can be reused by subsequent requests, allowing attackers to smuggle requests past access controls. This affects versions 8.0.0 through 8.1.11, 9.0.0 through 9.2.15, 10.0.0 through 10.1.4, and 10.2.0.
Affected products
- Apache Traffic Server 8.0.0 through 8.1.11, 9.0.0 through 9.2.15, 10.0.0 through 10.1.4, 10.2.0
Timeline
- 2026-10-21: disclosed