CVE-2026-103119: Apache Tomcat: AJP response mix-up
Buffer under-read vulnerability in Apache Tomcat meant that a large non-blocking write could result in the response body being split between the current request and the next request received on that connection leading most likely to failure of the second request and possibly leakage of data from the first response to the second. This issue affects Apache Tomcat: from 11.0.0-M25 through 11.0.26. Users are recommended to upgrade to version 11.0.27, which fixes the issue.
Other sources
Buffer under-read vulnerability in Apache Tomcat meant that a large non-blocking write could result in the response body being split between the current request and the next request received on that connection leading most likely to failure of the second request and possibly leakage of data from the first response to the second.
This issue affects Apache Tomcat: from 11.0.0 through 11.0.26.
Users are recommended to upgrade to version 11.0.27, which fixes the issue.
— OSV
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
bitnami/tomcatto a version that resolves this vulnerability.Fixed in 11.0.27 - Upgrade
Upgrade
Apache Tomcatto a version that resolves this vulnerability.Fixed in 11.0.27
Event History
Frequently Asked Questions
Which deployments are affected?
Apache Tomcat versions from 11.0.0-M25 through 11.0.26 are affected. The issue is associated with AJP handling and a large non-blocking write.
What conditions are needed for exploitation?
An attacker can exploit the issue remotely without privileges or user interaction. The vulnerable condition occurs when a large non-blocking write causes response data to be split between the current request and the next request on the same connection.
What is the practical impact?
The next request on the connection will most likely fail. Data from the first response may also be leaked in the response to the second request.
How should affected systems be remediated?
Upgrade Apache Tomcat to version 11.0.27, which fixes the issue.