dbcve.org
TomcatWeb server / proxy · Apache

CVE-2026-32990

MEDIUM · 5.3 CVSS v3.1 Published 2026-04-09
Fix available
A fix is available. Upgrade to 9.0.116 / 10.1.53 or later.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Improper Input Validation vulnerability in Apache Tomcat due to an incomplete fix of CVE-2025-66614. This issue affects Apache Tomcat: from 11.0.15 through 11.0.19, from 10.1.50 through 10.1.52, from 9.0.113 through 9.0.115. Users are recommended to upgrade to version 11.0.20, 10.1.53 or 9.0.116, which fix the issue.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

This is an improper input validation vulnerability in Apache Tomcat representing an incomplete fix of CVE-2025-66614. The vulnerability allows potential security bypass through improper input handling in affected Tomcat versions.

MitigationUpgrade Apache Tomcat to version 9.0.116, 10.1.53, or 11.0.20 (or later) to resolve this incomplete fix from the previous CVE.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
TomcatWeb server / proxy
Affected:>= 9.0.113, < 9.0.116>= 10.1.50, < 10.1.53>= 11.0.15, < 11.0.20

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
None

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Determine installed Apache Tomcat version
    Check the release notes or version file in the Tomcat installation directory, typically found in the RELEASE-NOTES file or by examining the server info via the manager web application or server.xml header comments
    Affected if The version displayed falls within 9.0.113-9.0.115, 10.1.50-10.1.52, or 11.0.15-11.0.19
  2. Identify the major Tomcat branch
    The version number structure indicates the branch: 9.0.x is Tomcat 9, 10.1.x is Tomcat 10.1, 11.0.x is Tomcat 11
    Affected if Running any of the three affected version branches within the ranges listed above
  3. Verify if Tomcat is handling external input
    Check if the Tomcat instance exposes any web applications, servlets, or connectors that process external HTTP requests or form inputs
    Affected if The server accepts and processes external HTTP requests, as the vulnerability involves input validation during request processing

You are affected if your installed Apache Tomcat version is 9.0.113 through 9.0.115, 10.1.50 through 10.1.52, or 11.0.15 through 11.0.19, and the server processes external input through web applications or connectors.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 9.0.116 / 10.1.53 / 11.0.20 or later
Fixed in 9.0.11610.1.5311.0.20
Interim mitigation

Upgrade Apache Tomcat to version 9.0.116, 10.1.53, or 11.0.20 (or later) to resolve this incomplete fix from the previous CVE.

Recommended fix High confidence

9.0.116 for 9.0.x, 10.1.53 for 10.1.x, or 11.0.20 for 11.0.x

  1. 1. Identify current Apache Tomcat version by checking the $CATALINA_HOME/README or running 'catalina.sh version'
  2. 2. Determine the appropriate upgrade target: for 9.0.x upgrade to 9.0.116, for 10.1.x upgrade to 10.1.53, for 11.0.x upgrade to 11.0.20
  3. 3. Download the corresponding binary distribution from https://tomcat.apache.org/download-90.cgi, https://tomcat.apache.org/download-10.cgi, or https://tomcat.apache.org/download-11.cgi
  4. 4. Stop the Tomcat service/application
  5. 5. Create a complete backup of the existing Tomcat installation directory including conf, webapps, and any custom libraries
  6. 6. Extract the new version to a temporary location
  7. 7. Copy configuration files (server.xml, context.xml, etc.) and any custom libraries from the backup to the new installation
  8. 8. Deploy web applications from the backup webapps directory to the new installation
Caveat Review Tomcat migration notes for breaking changes between minor versions; major version jumps (e.g., 9.x to 10.x) have significant API changes

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Tomcat Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-32990 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-32990 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data