CVE-2026-84181
Description
A flaw was found in the Apache Camel Shiro component. The security processor fails to verify user credentials when an incoming request matches the identity of an authenticated user still associated with a reused worker thread. Under specific timing conditions, a remote attacker can exploit this issue by submitting requests naming an active user without valid credentials, resulting in authentication bypass and unauthorized access to sensitive information.
Statement
This vulnerability is rated as Moderate impact because an authentication bypass requires specific timing conditions and worker thread reuse, introducing high attack complexity. In Red Hat environments, the issue only affects Apache Camel routes explicitly configured to use the camel-shiro security component. An unauthenticated request can only succeed if it specifies the principal of an active user whose session happens to be currently bound to an assigned thread from the worker pool.
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).
The following CVSS metrics and score provided are preliminary and subject to review.
CVSS v3 Score Breakdown
| Red Hat | NVD | cve.org | |
|---|---|---|---|
| Base Score | 5.9 | N/A | 5.9 |
| Attack Vector | Network | N/A | Network |
| Attack Complexity | High | N/A | High |
| Privileges Required | None | N/A | None |
| User Interaction | None | N/A | None |
| Scope | Unchanged | N/A | Unchanged |
| Confidentiality | High | N/A | High |
| Integrity Impact | None | N/A | None |
| Availability Impact | None | N/A | None |
Vector
Red Hat: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
cve.org: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
Understanding the Weakness (CWE)
Confidentiality
Technical Impact: Read Application Data
Data can "bleed" from one session to another through member variables of singleton objects, such as Servlets, and objects from a shared pool. Storing user data in Servlet member fields introduces a data access race condition.
Frequently Asked Questions
Not sure what something means? Check out our Security Glossary.
Want to get errata notifications? Sign up here.
