CVE-2026-32990
Improper Input Validation in Apache Tomcat Allows Potential Exploits
Publication date: 2026-04-09
Last updated on: 2026-04-14
Assigner: Apache Software Foundation
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| apache | tomcat | From 10.1.50 (inc) to 10.1.53 (exc) |
| apache | tomcat | From 11.0.15 (inc) to 11.0.20 (exc) |
| apache | tomcat | From 9.0.113 (inc) to 9.0.116 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-20 | The product receives input or data, but it does not validate or incorrectly validates that the input has the properties that are required to process the data safely and correctly. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability is an Improper Input Validation issue in Apache Tomcat. It arises because a previous fix for CVE-2025-66614 was incomplete, leaving the software still vulnerable. The affected versions are Apache Tomcat from 11.0.15 through 11.0.19, 10.1.50 through 10.1.52, and 9.0.113 through 9.0.115.
Improper Input Validation means that the software does not correctly check or sanitize input data, which can lead to unexpected behavior or security issues.
What immediate steps should I take to mitigate this vulnerability?
Users are recommended to upgrade Apache Tomcat to versions 11.0.20, 10.1.53, or 9.0.116, which fix the issue caused by improper input validation.
How can this vulnerability impact me? :
This vulnerability is an Improper Input Validation issue in Apache Tomcat caused by an incomplete fix of a previous vulnerability (CVE-2025-66614). It affects multiple versions of Apache Tomcat (from 11.0.15 through 11.0.19, 10.1.50 through 10.1.52, and 9.0.113 through 9.0.115).
If exploited, this vulnerability could potentially allow attackers to bypass input validation controls, which may lead to unexpected behavior or security issues in applications running on affected Tomcat versions.
Users are recommended to upgrade to fixed versions (11.0.20, 10.1.53, or 9.0.116) to mitigate this risk.