CVE-2026-5795

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.

Published: 2026-04-08 Last update: 2026-04-23 Assigner: [email protected] Source: [email protected]
NVD Status：Analyzed，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2026-5795 is rated Low Risk (31.1/100): CVSS High severity, with low exploitation likelihood (EPSS 0.02%). Monitor for updates and reassess as exploit intelligence or EPSS changes.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2026-5795

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-04-09 — 0.02% —

Full EPSS history (1 record total)

Common vulnerability scoring system (CVSS) metrics for CVE-2026-5795

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
7.4 3.1 HIGH
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:H)
Even with access, the exploit needs extra luck, timing, or a fussy environment to actually work.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:N)
Service keeps running; no real outage angle.
 2.2 5.2 [email protected]

Weakness enumeration for CVE-2026-5795

GitHub Security Advisory for CVE-2026-5795

GHSA-r7p8-xq5m-436c · Severity: high · Ecosystem: maven — Eclipse Jetty: Early return from the JASPIAuthenticator code can potentially no clear ThreadLocal variables

OS Trackers for CVE-2026-5795

vendor priority summary link
debian not yet assigned CVE-2026-5795 not yet assigned priority: Debian including 2 source packages (jetty12, jetty9), 8 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): open 8. https://security-tracker.debian.org/tracker/CVE-2026-5795
redhat high — https://access.redhat.com/security/cve/CVE-2026-5795
suse high — https://www.suse.com/security/cve/CVE-2026-5795/
ubuntu medium CVE-2026-5795 medium priority: Ubuntu including 2 source packages (jetty, jetty9), 13 status rows across 8 suites (bionic, focal, jammy, noble, questing, trusty, upstream, xenial): needs-triage 10, DNE 3. https://ubuntu.com/security/CVE-2026-5795

Affected software / configurations for CVE-2026-5795

Vendor Product Version Raw CPE
eclipse jetty >= 9.4.0, <= 9.4.58 cpe:2.3:a:eclipse:jetty:*:*:*:*:*:*:*:*
eclipse jetty >= 10.0.0, <= 10.0.26 cpe:2.3:a:eclipse:jetty:*:*:*:*:*:*:*:*
eclipse jetty >= 11.0.0, <= 11.0.26 cpe:2.3:a:eclipse:jetty:*:*:*:*:*:*:*:*
eclipse jetty >= 12.0.0, < 12.0.34 cpe:2.3:a:eclipse:jetty:*:*:*:*:*:*:*:*
eclipse jetty >= 12.1.0, < 12.1.8 cpe:2.3:a:eclipse:jetty:*:*:*:*:*:*:*:*

References for CVE-2026-5795

cvelogic Threat Intelligence