CVE REMEDIATION GUIDE
Review reviewHighFixed-version data available

CVE-2026-5795 remediation guide

Eclipse Foundation Eclipse Jetty, HawtIO HawtIO 4.4.0, Red Hat build of Apache Camel 4.18.1 for Spring Boot 3.5.14

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.

Open CVE record
ProductEclipse Foundation Eclipse Jetty, HawtIO HawtIO 4.4.0, Red Hat build of Apache Camel 4.18.1 for Spring Boot 3.5.14
Affected versions>= 12.1.0 <= 12.1.7, >= 12.0.0 <= 12.0.33, >= 11.0.0 <= 11.0.28, >= 10.0.0 <= 10.0.28, >= 9.4.0 <= 9.4.60, >= 9.4.0 <= 9.4.58, >= 10.0.0 <= 10.0.26, >= 11.0.0 <= 11.0.26, >= 12.0.0 < 12.0.34, >= 12.1.0 < 12.1.8
Fixed versions12.0.34, 12.1.8
Priority basisReview · CVSS 7.4 · EPSS 0.53%
01

Identify the affected asset

Confirm whether Eclipse Foundation Eclipse Jetty, HawtIO HawtIO 4.4.0, Red Hat build of Apache Camel 4.18.1 for Spring Boot 3.5.14 is installed, record the deployed version and installation path, and identify exposed interfaces.

  • Record the product name, package or appliance identifier, and installed version.
  • Identify internet-facing, administrative, API, and internal access paths.
  • Preserve the pre-change configuration and relevant service logs.
02

Validate the affected-version match

Compare the deployed version with the affected range: >= 12.1.0 <= 12.1.7, >= 12.0.0 <= 12.0.33, >= 11.0.0 <= 11.0.28, >= 10.0.0 <= 10.0.28, >= 9.4.0 <= 9.4.60, >= 9.4.0 <= 9.4.58, >= 10.0.0 <= 10.0.26, >= 11.0.0 <= 11.0.26, >= 12.0.0 < 12.0.34, >= 12.1.0 < 12.1.8. Treat incomplete inventory results as unresolved.

03

Prioritize with independent signals

The CVSS severity warrants an early asset and exposure review. Combine this signal with asset criticality, exposure, compensating controls, and business impact.

04

Apply supported remediation

Follow the vendor advisory or supported update path. Current fixed-version status: 12.0.34, 12.1.8. Preserve configuration and rollback material before change.

05

Verify the result

Confirm the resulting version, service health, authentication and access paths, monitoring coverage, and relevant security logs.

  • Confirm the expected version and package state.
  • Run a functional health check for critical service paths.
  • Review authentication, error, application, and security monitoring logs.
  • Reassess exposure if the supported fix cannot be applied.

Operational boundary

This page does not replace the vendor advisory, support contract, change-management process, or recovery plan. Do not infer that an asset is unaffected from an incomplete inventory query or a missing fixed-version field.