High, CVSS 7.4MavenPublished
Eclipse Jetty: Early return from the JASPIAuthenticator code can potentially no clear ThreadLocal variables
CVE-2026-5795 · GHSA-r7p8-xq5m-436c
- Affected
- Maven org.eclipse.jetty.ee9:jetty-ee9-jaspi >= 12.1.0, <= 12.1.7; >= 12.0.0, <= 12.0.33
- Fixed in
- 12.0.3412.1.8· Vendor fix available
- Issue
- (as reported) A security vulnerability has been identified in Jetty's JaspiAuthenticator.java. The root cause is a failure to consistently clear authentication metadata stored in ThreadLocal during certain error or incomplete authentication flows. Specifically, after a GroupPrincipalCallback is persisted into the ThreadLocal, the authentication process may exit prematurely — before the ThreadLocal storage is cleared — if a mandatory CallerPrincipalCallback is missing or an exception occurs. This allows a subsequent, unprivileged user processed by the same worker thread to inherit these residual security roles, leading to Broken Access Control and Privilege Escalation. See also attached PDF. Impact An unauthenticated user may gain ungrated privileges from a previous request (privilege escalation). Patches No patches yet. Workarounds Do not use Jetty's JASPI.
Recommended action: Upgrade to 12.1.8 or 12.0.34 by release line, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.