CVE-2026-5795: In Eclipse Jetty, the class JASPIAuthenticator initiates the authentication checks, which set two ThreadLoc...
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.
Security readout for executives and security teams
Plain-English summary
CVE-2026-5795 is a Jetty authentication flaw that can let one request inherit authentication state left behind by another request on the same server thread. In affected deployments, this can break access control and allow privilege escalation. The supplied sources rate it high severity, but do not show active exploitation.
Executive priority
Treat as a high-priority remediation item for internet-facing or sensitive Jetty applications using JASPI authentication. It threatens confidentiality and integrity through possible privilege escalation, but current supplied evidence does not support emergency active-exploitation handling.
Technical view
Jetty JASPIAuthenticator can return early after setting two ThreadLocal variables without clearing them. If a later request reuses that thread, stale authentication context can be inherited, causing broken access control. The CVSS 3.1 score is 7.4 with high confidentiality and integrity impact and high attack complexity.
Likely exposure
Exposure is most likely in applications running Eclipse Jetty versions or branches listed as affected and using JASPI/JASPIAuthenticator-based authentication. Products embedding Jetty may also require review. The source bundle does not provide complete fixed-version mapping.
Exploitation context
The source bundle marks KEV as false and provides no cited evidence of active exploitation. Network reachability and no required privileges increase concern, but CVSS marks attack complexity high, suggesting exploitation depends on specific request timing, thread reuse, or application conditions.
Researcher notes
Key uncertainty is exact affected and fixed patch-level versions; the bundle lists major/minor baselines and external advisories, but not detailed version ranges. Focus validation on JASPIAuthenticator usage, ThreadLocal cleanup behavior, and whether downstream vendors backported fixes.
Mitigation direction
Review Eclipse Jetty advisory GHSA-r7p8-xq5m-436c for fixed-version guidance.
Apply applicable Red Hat RHSA updates for Red Hat-packaged Jetty components.
Inventory applications embedding Jetty, not only standalone Jetty servers.
Prioritize systems using JASPI or JASPIAuthenticator authentication paths.
If fixed versions are unclear, follow vendor guidance before changing authentication design.
Validation and detection
Identify Jetty versions 9.4.0, 10.0.0, 11.0.0, 12.0.0, and 12.1.0 in use.
Check whether deployed applications enable JASPI or JASPIAuthenticator.
Review dependency trees for embedded Jetty packages in Java applications.
Confirm vendor advisory applicability for Red Hat-distributed components.
After updates, verify the running Jetty package version against vendor guidance.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-226: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Authentication and credential weaknesses can make valid-account abuse and credential telemetry useful review starting points. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references privilege impact, so privilege escalation and authorization behavior review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
2CVSS vectors
5Timeline events
2ADP providers
9Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: total
CVSS vector scores
2 official scores
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-226 · source CWE mapping
Sensitive Information in Resource Not Removed Before Reuse
Sensitive Information in Resource Not Removed Before Reuse represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Improper Authentication represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.