cve.bz

CVE-2026-5795 eclipse jetty: Improper Authentication

7.4 highEPSS 0.5%Fix available

High (7.4) in eclipse jetty. EPSS 0.5% estimated probability of exploitation activity in the next 30 days. Fixed in org.eclipse.jetty.ee11:jetty-ee11-jaspi 12.0.34, 12.1.8.

On this page
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.

Severity

CVSS 3.1

7.4 high
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N
EPSS
0.5% (unchanged from 0.5% a week ago; 0.6% 30 days ago) estimated probability of exploitation activity in the next 30 days; 46th percentile. Scored 2026-11-21. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: total, assessed 2026-04-08. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWEs
CWE-226 Sensitive Information in Resource Not Removed Before Reuse
CWE-287 Improper Authentication
OWASP Top 10
A07:2025 Authentication Failures
Published
Modified
NVD analysis
Analyzed, since modified
Record from
the NVD, synced

Fix and patched versions

  • org.eclipse.jetty.ee11:jetty-ee11-jaspi (Maven): fixed in 12.1.8, 12.0.34
  • org.eclipse.jetty.ee10:jetty-ee10-jaspi (Maven): fixed in 12.1.8, 12.0.34
  • org.eclipse.jetty.ee9:jetty-ee9-jaspi (Maven): fixed in 12.1.8, 12.0.34
  • org.eclipse.jetty.ee8:jetty-ee8-jaspi (Maven): fixed in 12.1.8, 12.0.34
  • org.eclipse.jetty:jetty-jaspi (Maven): fixed in 11.0.29, 10.0.29, 9.4.61
  • Debian, openSUSE: fixed package versions per release

Ask an AI about this CVE

Show the promptExplain CVE-2026-5795 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-5795?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-5795?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-5795 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
Eclipse Foundation Eclipse Jettyfrom 12.1.0 through 12.1.7
Eclipse Foundation Eclipse Jettyfrom 12.0.0 through 12.0.33
Eclipse Foundation Eclipse Jettyfrom 11.0.0 through 11.0.28
Eclipse Foundation Eclipse Jettyfrom 10.0.0 through 10.0.28
Eclipse Foundation Eclipse Jettyfrom 9.4.0 through 9.4.60

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-r7p8-xq5m-436cMavenorg.eclipse.jetty.ee11:jetty-ee11-jaspi>=12.1.0 <12.1.812.1.8
GHSA-r7p8-xq5m-436cMavenorg.eclipse.jetty.ee10:jetty-ee10-jaspi>=12.1.0 <12.1.812.1.8
GHSA-r7p8-xq5m-436cMavenorg.eclipse.jetty.ee9:jetty-ee9-jaspi>=12.1.0 <12.1.812.1.8
GHSA-r7p8-xq5m-436cMavenorg.eclipse.jetty.ee8:jetty-ee8-jaspi>=12.1.0 <12.1.812.1.8
GHSA-r7p8-xq5m-436cMavenorg.eclipse.jetty.ee11:jetty-ee11-jaspi>=12.0.0 <12.0.3412.0.34
GHSA-r7p8-xq5m-436cMavenorg.eclipse.jetty.ee10:jetty-ee10-jaspi>=12.0.0 <12.0.3412.0.34
GHSA-r7p8-xq5m-436cMavenorg.eclipse.jetty.ee9:jetty-ee9-jaspi>=12.0.0 <12.0.3412.0.34
GHSA-r7p8-xq5m-436cMavenorg.eclipse.jetty.ee8:jetty-ee8-jaspi>=12.0.0 <12.0.3412.0.34
GHSA-r7p8-xq5m-436cMavenorg.eclipse.jetty:jetty-jaspi>=11.0.0 <11.0.2911.0.29
GHSA-r7p8-xq5m-436cMavenorg.eclipse.jetty:jetty-jaspi>=10.0.0 <10.0.2910.0.29
GHSA-r7p8-xq5m-436cMavenorg.eclipse.jetty:jetty-jaspi>=9.4.0 <9.4.619.4.61

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12, 14jetty9no fix listedDEBIAN-CVE-2026-5795
Debian13jetty9, jetty12no fix listedDEBIAN-CVE-2026-5795
Debian14jetty1212.0.39-1DEBIAN-CVE-2026-5795
Ubuntu14.04:LTSjettyno fix listedUBUNTU-CVE-2026-5795
Ubuntu16.04:LTSjetty, jetty9no fix listedUBUNTU-CVE-2026-5795
Ubuntu18.04:LTS, 20.04:LTS, 22.04:LTS and 4 morejetty9no fix listedUBUNTU-CVE-2026-5795
openSUSETumbleweedjetty-minimal9.4.58-4.1openSUSE-SU-2026:10574-1

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; SUSE security data, CC BY 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · openSUSE.

Red Hat

Red Hat rates this Important.

Red Hat's statement

This vulnerability is only exploitable when `JASPIAuthenticator` class returns early and a subsequent request inherits the un-cleared ThreadLocal values. This requires a new request to be assigned the exact same recycled thread, increasing the complexity of exploitation. Due to these reasons, this flaw has been rated with an important severity.

Red Hat's mitigation

Red Hat has investigated whether a possible mitigation exists for this issue, and has not been able to identify a practical example. Please update the affected package as soon as possible.

ProductPackageStateAdvisory
HawtIO HawtIO 4.4.0jetty-ee10-servletFixed 2026-06-10RHSA-2026:25089
HawtIO HawtIO 4.4.0jetty-ee10-webappFixed 2026-06-10RHSA-2026:25089
Red Hat build of Apache Camel 4.18.1 for Spring Boot 3.5.14jetty-ee10-annotationsFixed 2026-05-14RHSA-2026:17668
Red Hat build of Apache Camel 4.18.1 for Spring Boot 3.5.14jetty-ee10-apache-jspFixed 2026-05-14RHSA-2026:17668
Red Hat build of Apache Camel 4.18.1 for Spring Boot 3.5.14jetty-ee10-plusFixed 2026-05-14RHSA-2026:17668
Red Hat build of Apache Camel 4.18.1 for Spring Boot 3.5.14jetty-ee10-servletFixed 2026-05-14RHSA-2026:17668
Red Hat build of Apache Camel 4.18.1 for Spring Boot 3.5.14jetty-ee10-servletsFixed 2026-05-14RHSA-2026:17668
Red Hat build of Apache Camel 4.18.1 for Spring Boot 3.5.14jetty-ee10-webappFixed 2026-05-14RHSA-2026:17668
Red Hat Offline Knowledge Portal 1.2.13offline-knowledge-portal/rhokp-rhel9:1782239370Fixed 2026-06-23RHSA-2026:28573
Red Hat Data Grid 8jetty-ee10-servletNot affected
Red Hat JBoss Enterprise Application Platform 8jetty-ee10-annotationsNot affected
Red Hat JBoss Enterprise Application Platform 8jetty-ee10-apache-jspNot affected
Red Hat JBoss Enterprise Application Platform 8jetty-ee10-cdiNot affected
Red Hat JBoss Enterprise Application Platform 8jetty-ee10-fcgi-proxyNot affected
Red Hat JBoss Enterprise Application Platform 8jetty-ee10-glassfish-jstlNot affected
Red Hat JBoss Enterprise Application Platform 8jetty-ee10-homeNot affected
Red Hat JBoss Enterprise Application Platform 8jetty-ee10-jaspiNot affected
Red Hat JBoss Enterprise Application Platform 8jetty-ee10-jndiNot affected
Red Hat JBoss Enterprise Application Platform 8jetty-ee10-jspc-maven-pluginNot affected
Red Hat JBoss Enterprise Application Platform 8jetty-ee10-maven-pluginNot affected
26 more in the JSON and on Red Hat's page.

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-5795.

Attack patterns (CAPEC)

  • CAPEC-37 Retrieve Embedded Sensitive Data Likelihood: High · Severity: Very High
  • CAPEC-22 Exploiting Trust in Client Likelihood: High · Severity: High
  • CAPEC-57 Utilizing REST's Trust in the System Resource to Obtain Sensitive Data Likelihood: Medium · Severity: Very High
  • CAPEC-94 Adversary in the Middle (AiTM) Likelihood: High · Severity: Very High
  • CAPEC-114 Authentication Abuse Severity: Medium
  • CAPEC-115 Authentication Bypass Severity: Medium
  • CAPEC-151 Identity Spoofing Likelihood: Medium · Severity: Medium
  • CAPEC-194 Fake the Source of Data Severity: Medium
  • CAPEC-593 Session Hijacking Likelihood: High · Severity: Very High
  • CAPEC-633 Token Impersonation Severity: Medium

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits. More on the page of CWE-287.

References

Check your stackJSON