Eclipse Jetty: Sensitive Information in Resource Not Removed Before Reuse
CVE-2026-5795 is a high-severity sensitive information in resource not removed before reuse vulnerability in Eclipse Jetty from Eclipse Foundation, with a CVSS 3.1 base score of 7.4 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, without any action from a user. Affected Eclipse Jetty versions: 12.1.0 through 12.1.7; 12.0.0 through 12.0.33; 11.0.0 through 11.0.28, and others listed below. The record does not name a fixed version, so check the vendor advisory. There is no confirmed exploitation so far. EPSS estimates a 0.54% chance of exploitation within 30 days, which is low compared with other CVEs.
High severity with no evidence of exploitation so far.
What to do
- Update Jetty to 12.0.34 or 12.1.8, whichever matches your release line, or a later version.
- Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Eclipse Foundation | Eclipse Jetty | 12.1.0 through 12.1.7; 12.0.0 through 12.0.33; 11.0.0 through 11.0.28; 10.0.0 through 10.0.28; 9.4.0 through 9.4.60 | Not stated |
| Red Hat | HawtIO HawtIO 4.4.0 | Not specified in the record | Not stated |
| Red Hat | Red Hat build of Apache Camel 4.18.1 for Spring Boot 3.5.14 | Not specified in the record | Not stated |
| Red Hat | Red Hat Offline Knowledge Portal 1.2.12 | Not specified in the record | Not stated |
| Red Hat | Red Hat Data Grid 8 | Not specified in the record | Not stated |
| Red Hat | Red Hat JBoss Enterprise Application Platform 8 | Not specified in the record | Not stated |
| Red Hat | Red Hat JBoss Enterprise Application Platform Expansion Pack | Not specified in the record | Not stated |
| Red Hat | Red Hat OpenShift Dev Spaces | Not specified in the record | Not stated |
| Red Hat | streams for Apache Kafka 3 | Not specified in the record | Not stated |
| Eclipse | Jetty | 9.4.0 through 9.4.58; 10.0.0 through 10.0.26; 11.0.0 through 11.0.26; 12.0.0 up to, but not including, 12.0.34; 12.1.0 up to, but not including, 12.1.8 | 12.0.34, 12.1.8 |
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- NetworkCan be exploited remotely over a network, including the internet.
- Attack complexity
- HighSuccess depends on conditions outside the attacker's control.
- Privileges required
- NoneNo account or login is needed.
- User interaction
- NoneNo action by a victim is required.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- HighAll data handled by the component can be read.
- Integrity
- HighData or code can be modified at will.
- Availability
- NoneAvailability is not affected.
Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N. Scored by CNA (eclipse.org).
| Scoring system | Score | Severity | Scored by |
|---|---|---|---|
| CVSS 3.1 | 7.4 | High | CNA (eclipse.org) |
| CVSS 3.1 | 7.4 | High | CNA |
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.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Sensitive Information in Resource Not Removed Before Reuse
The product releases a resource such as memory or a file so that it can be made available for reuse, but it does not clear or zeroize the information contained in the resource before the product performs a critical state transition or makes the resource available for reuse by other entities.
How developers prevent this class of flaw
- During critical state transitions, information not needed in the next state should be removed or overwritten with fixed patterns (such as all 0's) or random data, before the transition to the next state.
- Be careful using vfork() and fork() in security sensitive code. The process state will not be cleaned up and will contain traces of data from past use.
More Sensitive Information in Resource Not Removed Before Reuse vulnerabilities (CWE-226)
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: total).
- Record last changed materially (score, affected products, status or references).
References
Other references
Other vulnerabilities in Eclipse Jetty
- 8.2 High severity
- 8.2 High severity
- 8.3 High severity
- 8.7 High severity
- 8.7 High severity
- 9.1 Critical severity
Recent Sensitive Information in Resource Not Removed Before Reuse vulnerabilities
- 7.5 High severity
- 7.9 High severity
Spotted an error? Tell us.