CVE-2026-5795
Severity
7.4HIGH
EPSS
0.0%
top 95.86%
CISA KEV
Not in KEV
Exploit
No known exploits
Affected products
Timeline
PublishedApr 8
Latest updateApr 14
Description
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.
CVSS vector
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:NExploitability: 2.2 | Impact: 5.2
Affected Packages7 packages
🔴Vulnerability Details
5GHSA▶
Eclipse Jetty: Early return from the JASPIAuthenticator code can potentially no clear ThreadLocal variables↗2026-04-14
VulDB▶
Eclipse Jetty up to 9.4.60/10.0.28/11.0.28/12.0.33/12.1.7 JASPIAuthenticator ThreadLocal sensitive information in resource not removed before reuse (Nessus ID 306024)↗2026-04-11
OSV▶
Eclipse Jetty: Early return from the JASPIAuthenticator code can potentially no clear ThreadLocal variables↗2026-04-08
GHSA▶
Eclipse Jetty: Early return from the JASPIAuthenticator code can potentially no clear ThreadLocal variables↗2026-04-08
CVEList▶
CVE-2026-5795: In Eclipse Jetty, the class JASPIAuthenticator initiates the authentication checks, which set two ThreadLocal variable↗2026-04-08
📋Vendor Advisories
1Red Hat▶
org.eclipse.jetty.ee10/jetty-ee10: early return from the JASPIAuthenticator class without clearing ThreadLocal variables↗2026-04-08
🕵️Threat Intelligence
1💬Community
1Bugzilla▶
CVE-2026-5795 org.eclipse.jetty.ee10/jetty-ee10: early return from the JASPIAuthenticator class without clearing ThreadLocal variables↗2026-04-08