TomcatWeb server / proxy · Apache
CVE-2026-41293
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 · uneditedImproper Input Validation vulnerability in Apache Tomcat. This issue affects Apache Tomcat: from 11.0.0-M1 through 11.0.21, from 10.1.0-M1 through 10.1.54, from 9.0.0.M1 through 9.0.117, from 10.0.0-M1 through 10.0.27. Older, end of support versions may also be affected. Users are recommended to upgrade to version [FIXED_VERSION], which fixes 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 · moderate confidenceImproper Input Validation vulnerability in Apache Tomcat allows attackers to exploit insufficient validation of input data. The critical CVSS score of 9.8 indicates potential for complete compromise of confidentiality, integrity, and availability.
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
>= 8.5.0, <= 8.5.100>= 9.0.0, < 9.0.118>= 10.0.0, <= 10.0.27>= 10.1.0, < 10.1.55>= 11.0.0, < 11.0.22CVSS 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
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
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 checksWork through these to decide whether this CVE applies to you.
-
Identify Apache Tomcat versionLocate the Tomcat installation directory. Check the RELEASE-NOTES file in the Tomcat home directory, or run the version.sh (Linux) or version.bat (Windows) script from the bin folder. The output displays the Apache Tomcat version.Affected if The installed version falls within any of these ranges: 8.5.0-8.5.100, 9.0.0-9.0.117, 10.0.0-10.0.27, 10.1.0-10.1.54, or 11.0.0-11.0.21
-
Confirm Tomcat is running and network-accessibleCheck if the Tomcat service is running (for example, using systemctl status tomcat or checking process list). Verify network binding by reviewing the server.xml connector configuration, specifically the port and address attributes.Affected if Tomcat is running and bound to a network interface that accepts untrusted input (for example, 0.0.0.0 or a public IP address on HTTP connectors)
-
Identify exposed endpoints and connectorsReview the conf/server.xml file for active Connector definitions. Check which ports are listening (typically 8080 for HTTP). Identify any web applications deployed that process user-supplied input.Affected if HTTP connectors are enabled and web applications handle external input without additional input validation proxies
A user is affected if their Apache Tomcat version is within the affected ranges AND the server accepts network traffic on HTTP connectors that process untrusted input.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor data9.0.11810.1.5511.0.22
Upgrade Apache Tomcat to the fixed version to remediate this improper input validation vulnerability.
Fix this in Tomcat
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-41293 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-41293 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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