Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Unrated

Apache Tomcat: HTTP/2 request/response mix-up after error during async processing

CVE-2026-101356

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (tomcat 11.0.27, 10.1.61, 9.0.123), 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
    >= 9.0.118, < 9.0.123>= 10.1.55, < 10.1.61>= 11.0.22, < 11.0.27
    Fixed in
    10.1.61, 9.0.123, 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-101356: 0.50% estimated exploitation activity in the next 30 days; percentile 42.82 (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.

Incorrect object recycling and re-use vulnerability in Apache Tomcat affecting HTTP/2 processing of asynchronous servlets can trigger request and/or response mix-up between users. This issue affects Apache Tomcat: from 11.0.22 through 11.0.26, from 10.1.55 through 10.1.60, from 9.0.118 through 9.0.122. Users are recommended to upgrade to version 11.0.27, 10.1.61 or 9.0.123, 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-101356

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-101356

Advisory: Apache Tomcat: HTTP/2 request/response mix-up after error during async processing
IDs: CVE-2026-101356
Record: https://patchnext.com/advisories/cve-2026-101356 (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, 10.1.61, 9.0.123. A vendor fix does not mean a deployment is fixed.

## Affected components
- Bitnami tomcat: affected >= 9.0.118, < 9.0.123; >= 10.1.55, < 10.1.61; >= 11.0.22, < 11.0.27; fixed in 10.1.61, 9.0.123, 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-101356 (OSV record BIT-tomcat-2026-101356 lists affected ranges: Bitnami tomcat >=9.0.118 =10.1.55 =11.0.22 <11.0.27 (fixed))

Commands are suggestions: review each one before running it.

Loading voting…