CVE Tools

CVE-2026-103119

Apache Tomcat: AJP response mix-up

No known exploitation. EPSS puts it in the 48th percentile. No fix published yet.

Check it yourself

No ready-made check. Neither Nuclei nor OpenVAS has one for this CVE yet.

Request a scan

Published Updated Sources: CVE.org, NVD

What to do

No fixed build or workaround is published yet. Limit exposure and watch for a patch.

  • Apache Software Foundation Apache TomcatAffected: ≥ 11.0.0-M25, ≤ 11.0.26Upgrade to: after 11.0.26Stated by: CVE record

Versions as the sources state them. Full version matrix after sign-in

Steps

Written by AI from the record
  1. Check which version of Apache Tomcat your servers run, especially if you use the 11.0.x line.
  2. If you are running Apache Tomcat 11.0.0-M25 through 11.0.26, flag this to whoever manages your servers as a priority check.
  3. Upgrade to Apache Tomcat 11.0.27, which the developers say fixes this issue.
  4. If you cannot upgrade right away, ask your IT provider whether disabling or restricting the AJP connector is possible as a temporary measure.
  5. Confirm with your hosting provider or IT team once the upgrade is applied.

What it is

From the CVE record

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.

In plain language

Written by AI from the record

A bug in Apache Tomcat's AJP connector can cause one user's web response to get mixed up with another's, which could leak data or break requests, but there's no known patch confirmed yet and no sign anyone is exploiting it.

A buffer under-read (CWE-127) in Apache Tomcat's non-blocking write handling can cause response bodies to be split across connections, risking cross-request data leakage and request failures in versions 11.0.0-M25 through 11.0.26.

If you're affected

  • Customer data exposure
  • Response data leaked to wrong user
  • Service errors/failed requests
  • Operational disruption

Exploitation

Where each signal puts this CVE on the scale from published to confirmed exploited.

EPSS48th
CISA KEV

Not in the catalog. CISA has not confirmed exploitation.

Public exploits

No public exploit or proof of concept found in the sources we track.

EPSS

0.6% chance of exploitation activity in the next 30 days, which ranks it in the 48th percentile of scored CVEs.

Exploit Prediction Scoring System, FIRST.org. A probability, not a confirmation.

Lifecycle

4 events over 0 days, from the signal feeds we watch.

  1. Publishedweakness classified, record updated, record updated

Affected products

Technical detail

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

Scored 9.1 by NVD.

How it is reached

  • Attack Vector NetworkExploitable remotely over the network without any special conditions
  • Attack Complexity LowNo special conditions — the attack can be reliably reproduced
  • Privileges Required NoneNo authentication required — anyone can exploit this
  • User Interaction NoneNo user interaction needed — fully automated exploitation

Scope

  • Scope UnchangedImpact is limited to the vulnerable component itself

Impact if exploited

  • Confidentiality HighTotal information disclosure — all data in the component is compromised
  • Integrity NoneNo integrity impact
  • Availability HighTotal denial of service — the component is completely unavailable

Weaknesses

Sources

Watch the software you run.

My Stack ranks new CVEs for your products by real-world exploitation, so the next serious one reaches you without reading every advisory.

We'll flag the next CVE, public exploit or patch for Apache Tomcat, not every advisory.