Improper Authorization Affecting org.apache.tomcat:tomcat-catalina package, versions [9.0.25,9.0.121)[10.1.0-M1,10.1.58)[11.0.0-M1,11.0.25)
Threat Intelligence
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applicationsSnyk Learn
Learn about Improper Authorization vulnerabilities in an interactive lesson.
Start learning- Snyk IDSNYK-JAVA-ORGAPACHETOMCAT-19343977
- published27 Aug 2026
- disclosed26 Aug 2026
- credit4ra1n, pyn3rd, unam4
Introduced: 26 Aug 2026
NewCVE-2026-66422 (opens in a new tab)How to fix?
Upgrade org.apache.tomcat:tomcat-catalina to version 9.0.121, 10.1.58, 11.0.25 or higher.
Overview
org.apache.tomcat:tomcat-catalina is a Tomcat Servlet Engine Core Classes and Standard implementations.
Affected versions of this package are vulnerable to Improper Authorization through the Request.isUserInRole() and RealmBase.hasRole() role-checking paths in java/org/apache/catalina/connector/Request.java and java/org/apache/catalina/realm/RealmBase.java. An attacker can gain access to protected functionality by sending requests that rely on a security-role-ref mapping being treated as a general role alias. Because Tomcat applies security-role-ref definitions during realm authorization instead of limiting them to Request.isUserInRole(), a web application can authorize a user for a role that was only intended as a servlet-specific reference, causing access-control decisions to grant permissions the application did not intend to expose.
Notes
- The issue was fixed in Apache Tomcat 10.1.58, but the release vote for the 10.1.58 release candidate did not pass. Therefore, although users must download 10.1.59 to obtain a version that includes a fix for this issue, version 10.1.58 is not included in the list of affected versions.