Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Unrated

Apache Tomcat: AJP response mix-up

CVE-2026-103119

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (tomcat 11.0.27), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • Bitnami tomcat

    Affected
    >= 11.0.0, < 11.0.27
    Fixed in
    11.0.27

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
not scored
EPSS
  • CVE-2026-103119: 0.59% estimated exploitation activity in the next 30 days; percentile 48.07 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

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.

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 1 · created ·

    Published from osv record BIT-tomcat-2026-103119

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-103119

Advisory: Apache Tomcat: AJP response mix-up
IDs: CVE-2026-103119
Record: https://patchnext.com/advisories/cve-2026-103119 (revision 1, source checked 30 Oct 2026, 07:20 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Unrated
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: tomcat 11.0.27. A vendor fix does not mean a deployment is fixed.

## Affected components
- Bitnami tomcat: affected >= 11.0.0, < 11.0.27; fixed in 11.0.27

## Suggested inspection (read-only)
- Bitnami tomcat: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on tomcat.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/BIT-tomcat-2026-103119 (OSV record BIT-tomcat-2026-103119 lists affected ranges: Bitnami tomcat >=11.0.0 <11.0.27 (fixed))

Commands are suggestions: review each one before running it.

Loading voting…