CVE-2026-41284

Versions Affected:
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
Older, unsupported versions may also be affected

Description:
No limit was enforced on the request body for WebDAV LOCK or PROPFIND
requests which were available to unauthenticated users.

Mitigation:
Users of the affected versions should apply one of the following
mitigations:

• Upgrade to Apache Tomcat 11.0.22 or later
• Upgrade to Apache Tomcat 10.1.55 or later
• Upgrade to Apache Tomcat 9.0.118 or later

Credit:
This issue was identified by Dariusz Gońda

The application allocates resources such as memory, threads, or file descriptors based on untrusted input without enforcing a cap. Typical impact: resource exhaustion leading to denial of service.

CVE-2026-41284 has a CVSS score of 7.5 (High). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (9.0.118, 10.1.55, 11.0.22); upgrading removes the vulnerable code path.

Kodem intelligence

1. What is CVE-2026-41284? CVE-2026-41284 is a high-severity allocation of resources without limits or throttling vulnerability in org.apache.tomcat.embed:tomcat-embed-core (maven), affecting versions < 9.0.118. It is fixed in 9.0.118, 10.1.55, 11.0.22. The application allocates resources such as memory, threads, or file descriptors based on untrusted input without enforcing a cap.
2. How severe is CVE-2026-41284? CVE-2026-41284 has a CVSS score of 7.5 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which packages are affected by CVE-2026-41284?
   • org.apache.tomcat.embed:tomcat-embed-core (maven) (versions < 9.0.118)
   • org.apache.tomcat:tomcat (maven) (versions < 9.0.118)
   • org.apache.tomcat:tomcat-catalina (maven) (versions < 9.0.118)
4. Is there a fix for CVE-2026-41284? Yes. CVE-2026-41284 is fixed in 9.0.118, 10.1.55, 11.0.22. Upgrade to this version or later.
5. Is CVE-2026-41284 exploitable, and should I be worried? Whether CVE-2026-41284 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2026-41284 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2026-41284?
   • Upgrade org.apache.tomcat.embed:tomcat-embed-core to 9.0.118 or later
   • Upgrade org.apache.tomcat.embed:tomcat-embed-core to 10.1.55 or later
   • Upgrade org.apache.tomcat.embed:tomcat-embed-core to 11.0.22 or later
   • Upgrade org.apache.tomcat:tomcat to 9.0.118 or later
   • Upgrade org.apache.tomcat:tomcat to 10.1.55 or later
   • Upgrade org.apache.tomcat:tomcat to 11.0.22 or later
   • Upgrade org.apache.tomcat:tomcat-catalina to 9.0.118 or later
   • Upgrade org.apache.tomcat:tomcat-catalina to 10.1.55 or later
   • Upgrade org.apache.tomcat:tomcat-catalina to 11.0.22 or later