Is this vulnerability remotely exploitable?

Yes. An attacker who can send HTTP requests to a vulnerable Jetty instance can potentially exploit this issue by influencing how authentication flows execute and how threads are reused.

Does an attacker need valid credentials to exploit this?

Not necessarily. While having an account can make it easier to shape authentication flows, the core problem is the reuse of stale ThreadLocal state. In some scenarios, an unauthenticated attacker may benefit from a previous legitimate user's state being leaked onto their request.

What is the safest general fix pattern?

Ensure that all ThreadLocal-based authentication state is cleared in a guaranteed way, such as wrapping the entire authentication and request processing in a try/finally block that always removes or resets ThreadLocal values, even on early exit or error.

Severity:

HIGH RISK

(7.4)

Stale ThreadLocal Authentication State (CWE-226) in Eclipse Jetty JASPIAuthenticator

CVE-2026-5795

Published:

Apr 8, 2026

Status:

Analyzed

Summary

Affected Context

Exploit Preconditions

Why This Happens

Potential Impact

General Mitigation Guidance

How Teams Detect Issues Like This

Frequently Asked Questions

Source

NDV

Recent Vulnerabilities

CWE-94

HIGH RISK

HIGH

(8.8)

PHP Code Injection via File Upload (CWE-94) in Aero CMS Admin Post Creation

Remote Code Execution by authenticated users via malicious file upload

May 10, 2026

CWE-94

HIGH RISK

HIGH

(8.8)

Code Injection (CWE-94) via Module Parameters in Evolution CMS

Remote Code Execution by Authenticated Users

May 10, 2026

Vulnerability Type

Category:

Stale Authentication State / Race Conditions in Security Context

CWE:

CWE-226;CWE-287

Impact:

Broken Access Control and Privilege Escalation

Severity:

HIGH RISK

(7.4)

CVSS Version:

3.1

Vulnerability Type

Category:

Stale Authentication State / Race Conditions in Security Context

CWE:

CWE-226;CWE-287

Impact:

Broken Access Control and Privilege Escalation

Severity:

HIGH RISK

(7.4)

CVSS Version:

3.1

Catch This CVE While Code Is Being Written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Get Started

Ship clean & secure code faster

Start Free Trial

Get Pentest Report

Ship clean & secure code faster

Start Free Trial

Get Pentest Report

Ship clean & secure code faster

Start Free Trial

Get Pentest Report

CodeAnt AI is an offensive and defensive security platform.

Defensive + offensive security.

From first line of code to a pentest
that knows every line of it.

SOC 2 Type II certified | CodeAnt AI is independently audited and compliant with SOC 2 Type II security standards

Ask AI for summary of CodeAnt

Defensive + offensive security.

From first line of code to a pentest that knows every line of it.

Ask AI for summary of CodeAnt

Defensive + offensive security.

From first line of code to a pentest that knows every line of it.

Ask AI for summary of CodeAnt

Stale ThreadLocal Authentication State (CWE-226) in Eclipse Jetty JASPIAuthenticator

Summary

Affected Context

Exploit Preconditions

Why This Happens

Potential Impact

General Mitigation Guidance

How Teams Detect Issues Like This

Frequently Asked Questions

Source

Recent Vulnerabilities

HIGH RISK

HIGH

(8.8)

PHP Code Injection via File Upload (CWE-94) in Aero CMS Admin Post Creation

HIGH RISK

HIGH

(8.8)

Code Injection (CWE-94) via Module Parameters in Evolution CMS

Vulnerability Type

Vulnerability Type

Vulnerability Type

Catch This CVE While Code Is Being Written

Ship clean & secure code faster

Ship clean & secure code faster

Ship clean & secure code faster

Product

Compare

Company

Developers

Legal

Product

Compare

Company

Developers

Legal

Product

Compare

Company

Developers

Legal