# CVE-2026-5795: Eclipse Jetty: Early return from the JASPIAuthenticator code can potentially no clear ThreadLocal variables > Attackers can escalate privileges by exploiting uncleared ThreadLocal variables in Eclipse Jetty's JASPIAuthenticator, leading to broken access control. - **Severity:** High 7.4 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 8 Apr 2026 - **Updated:** 14 Sep 2026 - **Also known as:** CLEANSTART-2026-AM26944, CLEANSTART-2026-II62972, CLEANSTART-2026-NR53059, CLEANSTART-2026-RB25036, CLEANSTART-2026-ZS92015, CLSA-2026-1775781156, CLSA-2026-1775781158, CLSA-2026-1777336763, CLSA-2026-1778201085, CLSA-2026-1779324478, CLSA-2026-1779324480, CLSA-2026-1786437309, CLSA-2026-1786550111, DEBIAN-CVE-2026-5795, GHSA-r7p8-xq5m-436c, MINI-4vgc-gc3w-2mff, MINI-64cv-6qr7-3943, MINI-7p62-4qmc-xjp8, MINI-9vjp-x7m3-3qj7, ROOT-APP-MAVEN-CVE-2026-5795, UBUNTU-CVE-2026-5795 ## What is CVE-2026-5795? CVE-2026-5795 is a high-severity authentication bypass vulnerability in Eclipse Jetty, published on 8 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official 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. Weakness: CWE-287 (Improper Authentication), CWE-226 (Sensitive Information in Resource Not Removed Before Reuse) ## Which versions are affected by CVE-2026-5795? 22 open source packages ship an affected version, including org.eclipse.jetty:jetty-jaspi, org.eclipse.jetty.ee10:jetty-ee10-jaspi and org.eclipse.jetty.ee11:jetty-ee11-jaspi. It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `org.eclipse.jetty:jetty-jaspi` | Maven | From 10.0.0 | 10.0.29 | | `org.eclipse.jetty:jetty-jaspi` | Maven | From 10.0.0 | 10.0.29 | | `org.eclipse.jetty:jetty-jaspi` | Maven | From 11.0.0 | 11.0.29 | | `org.eclipse.jetty:jetty-jaspi` | Maven | From 11.0.0 | 11.0.29 | | `org.eclipse.jetty:jetty-jaspi` | Maven | From 9.4.0 | 9.4.61 | | `org.eclipse.jetty:jetty-jaspi` | Maven | From 9.4.0 | 9.4.61 | | `org.eclipse.jetty.ee10:jetty-ee10-jaspi` | Maven | From 12.0.0 | 12.0.34 | | `org.eclipse.jetty.ee10:jetty-ee10-jaspi` | Maven | From 12.0.0 | 12.0.34 | | `org.eclipse.jetty.ee10:jetty-ee10-jaspi` | Maven | From 12.1.0 | 12.1.8 | | `org.eclipse.jetty.ee10:jetty-ee10-jaspi` | Maven | From 12.1.0 | 12.1.8 | | `org.eclipse.jetty.ee11:jetty-ee11-jaspi` | Maven | From 12.0.0 | 12.0.34 | | `org.eclipse.jetty.ee11:jetty-ee11-jaspi` | Maven | From 12.0.0 | 12.0.34 | | `org.eclipse.jetty.ee11:jetty-ee11-jaspi` | Maven | From 12.1.0 | 12.1.8 | | `org.eclipse.jetty.ee11:jetty-ee11-jaspi` | Maven | From 12.1.0 | 12.1.8 | | `org.eclipse.jetty.ee8:jetty-ee8-jaspi` | Maven | From 12.0.0 | 12.0.34 | | `org.eclipse.jetty.ee8:jetty-ee8-jaspi` | Maven | From 12.0.0 | 12.0.34 | | `org.eclipse.jetty.ee8:jetty-ee8-jaspi` | Maven | From 12.1.0 | 12.1.8 | | `org.eclipse.jetty.ee8:jetty-ee8-jaspi` | Maven | From 12.1.0 | 12.1.8 | | `org.eclipse.jetty.ee9:jetty-ee9-jaspi` | Maven | From 12.0.0 | 12.0.34 | | `org.eclipse.jetty.ee9:jetty-ee9-jaspi` | Maven | From 12.0.0 | 12.0.34 | | `org.eclipse.jetty.ee9:jetty-ee9-jaspi` | Maven | From 12.1.0 | 12.1.8 | | `org.eclipse.jetty.ee9:jetty-ee9-jaspi` | Maven | From 12.1.0 | 12.1.8 | Products: Eclipse Jetty. ## How do I fix CVE-2026-5795? Upgrade org.eclipse.jetty:jetty-jaspi to a fixed version for your release line: 10.0.29, 11.0.29 or 9.4.61. ## Is CVE-2026-5795 being exploited? There is no known exploitation of CVE-2026-5795 in the wild and no public exploit code. ## Other vulnerabilities in Eclipse Jetty - [CVE-2016-4800](https://insights.sbomify.com/CVE-2016-4800/): Jetty contains an alias issue that could allow unauthenticated remote code execution due to specially crafted request (critical 9.8) - [CVE-2019-17638](https://insights.sbomify.com/CVE-2019-17638/): Operation on a Resource after Expiration or Release in Jetty Server (critical 9.4) - [CVE-2018-12538](https://insights.sbomify.com/CVE-2018-12538/): Access and integrity issue within Eclipse Jetty (high 8.8) - [CVE-2026-10050](https://insights.sbomify.com/CVE-2026-10050/): Digest authentication lossy encoding (high 8.7) - [CVE-2025-5115](https://insights.sbomify.com/CVE-2025-5115/): MadeYouReset HTTP/2 vulnerability (high 7.7) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2026-5795 and fix it if it is affected. What it is: CVE-2026-5795 is a high-severity authentication bypass vulnerability in Eclipse Jetty, published on 8 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim. Exploitation: There is no known exploitation of CVE-2026-5795 in the wild and no public exploit code. Affected packages and fixed versions: - org.eclipse.jetty:jetty-jaspi (Maven): affected from 10.0.0; fixed in 10.0.29 - org.eclipse.jetty:jetty-jaspi (Maven): affected from 10.0.0; fixed in 10.0.29 - org.eclipse.jetty:jetty-jaspi (Maven): affected from 11.0.0; fixed in 11.0.29 - org.eclipse.jetty:jetty-jaspi (Maven): affected from 11.0.0; fixed in 11.0.29 - org.eclipse.jetty:jetty-jaspi (Maven): affected from 9.4.0; fixed in 9.4.61 - org.eclipse.jetty:jetty-jaspi (Maven): affected from 9.4.0; fixed in 9.4.61 - org.eclipse.jetty.ee10:jetty-ee10-jaspi (Maven): affected from 12.0.0; fixed in 12.0.34 - org.eclipse.jetty.ee10:jetty-ee10-jaspi (Maven): affected from 12.0.0; fixed in 12.0.34 - org.eclipse.jetty.ee10:jetty-ee10-jaspi (Maven): affected from 12.1.0; fixed in 12.1.8 - org.eclipse.jetty.ee10:jetty-ee10-jaspi (Maven): affected from 12.1.0; fixed in 12.1.8 - org.eclipse.jetty.ee11:jetty-ee11-jaspi (Maven): affected from 12.0.0; fixed in 12.0.34 - org.eclipse.jetty.ee11:jetty-ee11-jaspi (Maven): affected from 12.0.0; fixed in 12.0.34 Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2026-5795/ (Markdown: https://insights.sbomify.com/CVE-2026-5795/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2026-5795 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-5795 - OSV: https://osv.dev/vulnerability/CVE-2026-5795 --- From sbomify Insights: https://insights.sbomify.com/CVE-2026-5795/ Summaries are generated and may contain mistakes; the official description above is the record.