CVE-2026-66422
Description
A flaw was found in Apache Tomcat. This improper authorization vulnerability occurs because security-role-ref definitions are incorrectly used as role aliases within the Realm, in addition to their correct usage with Request.isUserInRole(). This misconfiguration allows for a bypass of declarative role constraints, which could lead to unauthorized access to resources that should be restricted based on user roles.
Statement
This vulnerability is rated as Low impact. It requires high privileges to exploit and only affects the confidentiality of information by allowing a bypass of declarative role constraints. In Red Hat deployments, where Apache Tomcat instances are typically configured with strict access controls, this flaw primarily impacts already highly privileged users, limiting its overall risk.
Mitigation
Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability.
Common Vulnerability Scoring System (CVSS) Score Details
Info alert:Important note
CVSS scores for open source components depend on vendor-specific factors (e.g. version or build chain). Therefore, Red Hat's score and impact rating can be different from NVD and other vendors. Red Hat remains the authoritative CVE Naming Authority (CNA) source for its products and services (see Red Hat classifications).
CVSS v3 Score Breakdown
| Red Hat | NVD | cve.org | |
|---|---|---|---|
| Base Score | 2.7 | N/A | 8.1 |
| Attack Vector | Network | N/A | Network |
| Attack Complexity | Low | N/A | Low |
| Privileges Required | High | N/A | Low |
| User Interaction | None | N/A | None |
| Scope | Unchanged | N/A | Unchanged |
| Confidentiality | Low | N/A | None |
| Integrity Impact | None | N/A | High |
| Availability Impact | None | N/A | High |
Vector
Red Hat: CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:N/A:N
cve.org: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H
Understanding the Weakness (CWE)
Access Control
Technical Impact: Gain Privileges or Assume Identity
The attacker can gain access to otherwise unauthorized resources.
Integrity,Confidentiality,Other
Technical Impact: Modify Application Data; Modify Files or Directories; Read Application Data; Read Files or Directories; Other
Race conditions such as this kind may be employed to gain read or write access to resources not normally readable or writable by the user in question.
Integrity,Other
Technical Impact: Modify Application Data; Other
The resource in question, or other resources (through the corrupted one) may be changed in undesirable ways by a malicious user.
Non-Repudiation
Technical Impact: Hide Activities
If a file or other resource is written in this method, as opposed to a valid way, logging of the activity may not occur.
Non-Repudiation,Integrity
Technical Impact: Modify Files or Directories
In some cases it may be possible to delete files that a malicious user might not otherwise have access to -- such as log files.
Frequently Asked Questions
Not sure what something means? Check out our Security Glossary.
Want to get errata notifications? Sign up here.
