Attack Chain

1. An unauthenticated user sends an initial request to the Jetty server.
2. The JASPIAuthenticator class initiates authentication checks for the request.
3. The JASPIAuthenticator sets ThreadLocal variables to store authentication-related data.
4. Due to specific conditions (e.g., an error or incomplete authentication), the JASPIAuthenticator returns early without clearing the ThreadLocal variables.
5. A subsequent request from a different user (or even the same user) is processed by the same thread.
6. The JASPIAuthenticator reuses the thread, inheriting the stale ThreadLocal values from the previous request.
7. The inherited ThreadLocal values bypass or alter the authentication checks, granting the subsequent request unauthorized access.
8. The attacker gains elevated privileges or access to sensitive data due to the broken access control.

Impact

Successful exploitation of this vulnerability (CVE-2026-5795) results in broken access control and privilege escalation within the Eclipse Jetty server. An attacker could potentially gain unauthorized access to sensitive resources, perform actions on behalf of other users, or elevate their privileges to an administrative level. The exact impact depends on the specific configuration of the Jetty server and the resources it protects.

Recommendation

• Apply the patch or upgrade to a version of Eclipse Jetty that addresses CVE-2026-5795 to remediate the vulnerability.
• Monitor web server logs for anomalies related to authentication, particularly around the JASPIAuthenticator class, to detect potential exploitation attempts.
• Implement robust authentication and authorization mechanisms in your Jetty applications to minimize the impact of potential access control bypasses.