CVE-2026-5795

Description (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.

Workarounds

Do not use Jetty's JASPI.

An unauthenticated user may gain ungrated privileges from a previous request (privilege escalation).

The application does not adequately verify the identity of a user, device, or process before granting access. Typical impact: unauthorized access to functions or data reserved for authenticated parties.

CVE-2026-5795 has a CVSS score of 7.4 (High). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (12.1.8, 12.0.34, 11.0.29, 10.0.29, 9.4.61); upgrading removes the vulnerable code path.

Kodem intelligence

No patches yet.

1. What is CVE-2026-5795? CVE-2026-5795 is a high-severity improper authentication vulnerability in org.eclipse.jetty.ee11:jetty-ee11-jaspi (maven), affecting versions >= 12.1.0, <= 12.1.7. It is fixed in 12.1.8, 12.0.34, 11.0.29, 10.0.29, 9.4.61. The application does not adequately verify the identity of a user, device, or process before granting access.
2. How severe is CVE-2026-5795? CVE-2026-5795 has a CVSS score of 7.4 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which packages are affected by CVE-2026-5795?
   • org.eclipse.jetty.ee11:jetty-ee11-jaspi (maven) (versions >= 12.1.0, <= 12.1.7)
   • org.eclipse.jetty.ee10:jetty-ee10-jaspi (maven) (versions >= 12.1.0, <= 12.1.7)
   • org.eclipse.jetty.ee9:jetty-ee9-jaspi (maven) (versions >= 12.1.0, <= 12.1.7)
   • org.eclipse.jetty.ee8:jetty-ee8-jaspi (maven) (versions >= 12.1.0, <= 12.1.7)
   • org.eclipse.jetty:jetty-jaspi (maven) (versions >= 11.0.0, <= 11.0.28)
4. Is there a fix for CVE-2026-5795? Yes. CVE-2026-5795 is fixed in 12.1.8, 12.0.34, 11.0.29, 10.0.29, 9.4.61. Upgrade to this version or later.
5. Is CVE-2026-5795 exploitable, and should I be worried? Whether CVE-2026-5795 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2026-5795 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2026-5795?
   • Upgrade org.eclipse.jetty.ee11:jetty-ee11-jaspi to 12.1.8 or later
   • Upgrade org.eclipse.jetty.ee10:jetty-ee10-jaspi to 12.1.8 or later
   • Upgrade org.eclipse.jetty.ee9:jetty-ee9-jaspi to 12.1.8 or later
   • Upgrade org.eclipse.jetty.ee8:jetty-ee8-jaspi to 12.1.8 or later
   • Upgrade org.eclipse.jetty.ee11:jetty-ee11-jaspi to 12.0.34 or later
   • Upgrade org.eclipse.jetty.ee10:jetty-ee10-jaspi to 12.0.34 or later
   • Upgrade org.eclipse.jetty.ee9:jetty-ee9-jaspi to 12.0.34 or later
   • Upgrade org.eclipse.jetty.ee8:jetty-ee8-jaspi to 12.0.34 or later
   • Upgrade org.eclipse.jetty:jetty-jaspi to 11.0.29 or later
   • Upgrade org.eclipse.jetty:jetty-jaspi to 10.0.29 or later
   • Upgrade org.eclipse.jetty:jetty-jaspi to 9.4.61 or later