Widely used Apache Tomcat; high-severity flaw across multiple supported branches with potential remote compromise.
CVE-2026-41293
Improper input validation in Tomcat enables exploitation on multiple versions.
Is CVE-2026-41293 being exploited?
Not confirmed. CVE-2026-41293 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 1.7% probability of exploitation in the next 30 days.
How severe is CVE-2026-41293?
CVE-2026-41293 is rated Critical with a CVSS score of 9.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-41293?
Yes. A fix has been recorded for CVE-2026-41293. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-41293 affect?
CVE-2026-41293 affects Apache Tomcat 11.0.0-M1 to 11.0.21, Apache Tomcat 10.1.0-M1 to 10.1.54, Apache Tomcat 9.0.0.M1 to 9.0.117, Apache Tomcat 10.0.0-M1 to 10.0.27. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-41293?
Upgrade to the fixed Tomcat release immediately.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Remote code execution/server takeover via crafted input on affected Tomcat versions.
Immediate action required
- affected>= 11.0.0-M1 and <= 11.0.21
- affected>= 10.1.0-M1 and <= 10.1.54
- affected>= 9.0.0.M1 and <= 9.0.117
- affected>= 10.0.0-M1 and <= 10.0.27
- affected>= 8.5.0 and <= 8.5.100
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.