External risk intelligence

Apache Tomcat Buffer Under-read Vulnerability Can Leak Data

CVE advisorySeverity: CRITICAL (CVSS 9.1)

CVE-2026-103119

Apache Tomcat is a widely used web server and servlet container frequently deployed as an internet-facing application server or edge service to handle web traffic. Given its primary role in exposing web applications to users, it is commonly reachable from the public internet.

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

External exposure likelihood

Horizon Alert

Summary of the vulnerability and why it matters

A buffer under-read vulnerability in Apache Tomcat could lead to response data being split between requests, potentially causing the second request to fail and data from the first request to leak. This affects internet-facing web servers and servlet containers that handle user traffic.

  • Data leakage and request failures are possible.
  • Widely used web server technology is affected.
  • Confirm relevance and exposure for business systems.

Attack Path

How an attacker could exploit the issue

An attacker could exploit a buffer under-read vulnerability in Apache Tomcat by sending a specially crafted, large non-blocking write request. This could cause the response body to be incorrectly split between consecutive requests on the same connection, potentially leading to the failure of the second request and data leakage from the first.

  • Exposed to network, no authentication required.
  • Large non-blocking write request.
  • Request failure and potential data leakage.

Live Threat

Current exploitation, exposure, and threat context

A buffer under-read vulnerability in Apache Tomcat could lead to the response body being split between requests. This might cause the second request to fail and potentially leak data from the first response to the second when a large non-blocking write occurs on a shared connection.

  • Response data from previous requests.
  • Data may leak between requests.
  • Service instability and data exposure.

Operational Fix

Recommended remediation, mitigation, and detection steps

Real-World Ownership

This critical vulnerability in Apache Tomcat, a widely deployed web server, likely impacts teams responsible for hosting web applications or services. The first practical step is to inventory all Tomcat instances, assess their external reachability and business criticality, identify the accountable application or infrastructure owner, and then prioritize remediation efforts based on this risk assessment.

  • Application or Infrastructure Owners
  • Verify Tomcat instance reachability and criticality.
  • Plan coordinated upgrade or mitigation.

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 Tomcat?

Apache Tomcat is an open-source web server and servlet container. It provides a platform to run Java-based web applications, acting as the bridge between your website's code and the internet. Developers and organizations use it to host dynamic web content, manage user sessions, and handle incoming network requests for enterprise services.

What is a buffer under-read in CVE-2026-103119?

A buffer under-read (CWE-127) occurs when a program reads more data than it should from a memory area, often by reading before the start of a buffer. In this vulnerability, specifically, the server mismanages how it handles large non-blocking data writes, causing bits of one user's response to bleed into the next request's data stream.

How does an attacker trigger this bug?

The issue requires sending a very large, specifically timed non-blocking write request. If you are not using non-blocking I/O or do not process massive data writes on shared connections, your server may not trigger this behavior. It happens because the system gets confused about where one response ends and the next begins on the same active connection.

Is my server at risk according to Halo Surface Signal?

Halo Surface Signal notes that Apache Tomcat is frequently deployed as an internet-facing application server or edge service. Because these roles require Tomcat to handle direct web traffic from the public internet, it is often reachable by external parties. If your instance is exposed to the internet, it should be prioritized for review.

When should I upgrade my Tomcat software?

You should begin planning your upgrade as soon as possible if you run versions 11.0.0-M25 through 11.0.26. Your first step is to inventory all running Tomcat instances to determine which are internet-facing. Once identified, coordinate with your infrastructure team to update to version 11.0.27 to eliminate the risk of data leakage between requests.

References