Description (CNA)
In Eclipse Jetty, the class JASPIAuthenticator initiates the authentication checks, which set two ThreadLocal variable. Upon returning from the initial checks, there are conditions that cause an early return from the JASPIAuthenticator code without clearing those ThreadLocals. A subsequent request using the same thread inherits the ThreadLocal values, leading to a broken access control and privilege escalation.
Affected (CNA)
| Vendor / product | Versions |
|---|---|
| Eclipse Foundation / Eclipse Jetty | affected 12.1.0 through 12.1.7; affected 12.0.0 through 12.0.33; affected 11.0.0 through 11.0.28; affected 10.0.0 through 10.0.28; affected 9.4.0 through 9.4.60 |
CWE
CWE-226, CWE-287
References
- https://github.com/jetty/jetty.project/security/advisories/GHSA-r7p8-xq5m-436chttps://
- https://gitlab.eclipse.org/security/cve-assignment/-/issues/92
ADP enrichment
No English description supplied.
No references supplied.
A flaw was found in Eclipse Jetty. The `JASPIAuthenticator` class is responsible for handling authentication checks. During these checks, the class sets two ThreadLocal variables to store authentication state. Under certain conditions, the authentication process can return early without properly clearing the ThreadLocal variables, allowing a subsequent request to inherit the un-cleared ThreadLocal values. This issue can cause broken access control, authentication bypass, privilege escalation and data breaches.
- https://access.redhat.com/security/cve/CVE-2026-5795
- https://bugzilla.redhat.com/show_bug.cgi?id=2456519
- https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-5795.json
- https://access.redhat.com/errata/RHSA-2026:25089
- https://access.redhat.com/errata/RHSA-2026:28573
- https://access.redhat.com/errata/RHSA-2026:17668