Skip to content

Eclipse Jetty: Early return from the JASPIAuthenticator code can potentially no clear ThreadLocal variables

High severity GitHub Reviewed Published Apr 8, 2026 to the GitHub Advisory Database • Updated Apr 8, 2026

Package

maven org.eclipse.jetty.ee10:jetty-ee10 (Maven)

Affected versions

>= 12.1.0, < 12.1.7
>= 12.0.0, < 12.0.33
>= 11.0.0, < 11.0.28
>= 10.0.0, < 10.0.28
>= 9.4.0, < 9.4.60

Patched versions

12.1.7
12.0.33
11.0.28
10.0.28
9.4.60

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.

References

Published by the National Vulnerability Database Apr 8, 2026
Published to the GitHub Advisory Database Apr 8, 2026
Reviewed Apr 8, 2026
Last updated Apr 8, 2026

Severity

High

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
High
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N

EPSS score

Weaknesses

Sensitive Information in Resource Not Removed Before Reuse

The product releases a resource such as memory or a file so that it can be made available for reuse, but it does not clear or zeroize the information contained in the resource before the product performs a critical state transition or makes the resource available for reuse by other entities. Learn more on MITRE.

CVE ID

CVE-2026-5795

GHSA ID

GHSA-gc59-r5jq-98qw

Source code

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.