CVE-2026-5795 — jetty-ee11-jaspi
HIGHCVE-2026-5795 is a high-severity (CVSS 7.4) CWE-226 vulnerability in org.eclipse.jetty.ee11:jetty-ee11-jaspi. A fix is available for org.eclipse.jetty.ee11:jetty-ee11-jaspi — see the affected versions and patch details below.
Eclipse Jetty: Early return from the JASPIAuthenticator code can potentially no clear ThreadLocal variables
Exploitation Status
No confirmed exploitation observed yet
- A successful exploit gives an attacker total control of the affected component, not partial access.
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for CVE-2026-5795.
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
How urgent is this, really
CVE-2026-5795 plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.
Where this sits among everything scored
Of 377,166 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.
Real-World Exposure
org.eclipse.jetty.ee11:jetty-ee11-jaspi☕org.eclipse.jetty.ee10:jetty-ee10-jaspi☕org.eclipse.jetty.ee9:jetty-ee9-jaspi☕org.eclipse.jetty.ee8:jetty-ee8-jaspi☕org.eclipse.jetty.ee11:jetty-ee11-jaspi☕org.eclipse.jetty.ee10:jetty-ee10-jaspi☕org.eclipse.jetty.ee9:jetty-ee9-jaspi☕org.eclipse.jetty.ee8:jetty-ee8-jaspi+3 moreReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.
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.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.eclipse.jetty.ee11:jetty-ee11-jaspi | ≥ 12.1.0&&< 12.1.8 | 12.1.8org.eclipse.jetty.ee11:jetty-ee11-jaspi:12.1.8 |
| ☕Maven | org.eclipse.jetty.ee10:jetty-ee10-jaspi | ≥ 12.1.0&&< 12.1.8 | 12.1.8org.eclipse.jetty.ee10:jetty-ee10-jaspi:12.1.8 |
| ☕Maven | org.eclipse.jetty.ee9:jetty-ee9-jaspi | ≥ 12.1.0&&< 12.1.8 | 12.1.8org.eclipse.jetty.ee9:jetty-ee9-jaspi:12.1.8 |
| ☕Maven | org.eclipse.jetty.ee8:jetty-ee8-jaspi | ≥ 12.1.0&&< 12.1.8 | 12.1.8org.eclipse.jetty.ee8:jetty-ee8-jaspi:12.1.8 |
| ☕Maven | org.eclipse.jetty.ee11:jetty-ee11-jaspi | ≥ 12.0.0&&< 12.0.34 | 12.0.34org.eclipse.jetty.ee11:jetty-ee11-jaspi:12.0.34 |
| ☕Maven | org.eclipse.jetty.ee10:jetty-ee10-jaspi | ≥ 12.0.0&&< 12.0.34 | 12.0.34org.eclipse.jetty.ee10:jetty-ee10-jaspi:12.0.34 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.eclipse.jetty.ee11:jetty-ee11-jaspi, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.eclipse.jetty.ee11:jetty-ee11-jaspi to 12.1.8 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-5795 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2026-5795 can be triaged on real exposure rather than presence alone.
Tailored to CVE-2026-5795. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Fixing This On Your OS
If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.
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…
| Product | Fixed in | Advisory |
|---|---|---|
| HawtIO HawtIO 4.4.0 | jetty-ee10-servlet | RHSA-2026:25089 |
| Red Hat build of Apache Camel 4.18.1 for Spring Boot 3.5.14 | jetty-ee10-annotations | RHSA-2026:17668 |
| Red Hat Offline Knowledge Portal 1.2.12 | offline-knowledge-portal/rhokp-rhel9:1782239370 | RHSA-2026:28573 |
Frequently Asked Questions
Is CVE-2026-5795 in your dependencies?
O3 Security finds CVE-2026-5795 across Maven dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.