CVE-2026-85245
Description
A flaw was found in the Apache Camel Thrift component, which can lead to information disclosure. When processing incoming messages, the component unmarshals data into a shared process-wide object rather than creating a fresh instance for each exchange. Consequently, data from earlier or concurrent transactions remains accessible, allowing an attacker to observe sensitive information belonging to other users or tenants sharing the same route.
Statement
This vulnerability is rated Moderate due to the high attack complexity and specific multi-user conditions required to trigger information disclosure across transactions. Red Hat environments are only affected if integration routes explicitly incorporate the camel-thrift data format to unmarshal incoming messages from distinct, untrusted clients. Deployments where Camel routes operate in single-tenant architectures or process payloads within isolated processing contexts are not exposed to inter-session data leakage.
Common Vulnerability Scoring System (CVSS) Score Details
Info alert:Important note
CVSS scores for open source components depend on vendor-specific factors (e.g. version or build chain). Therefore, Red Hat's score and impact rating can be different from NVD and other vendors. Red Hat remains the authoritative CVE Naming Authority (CNA) source for its products and services (see Red Hat classifications).
The following CVSS metrics and score provided are preliminary and subject to review.
CVSS v3 Score Breakdown
| Red Hat | NVD | cve.org | |
|---|---|---|---|
| Base Score | 5.9 | N/A | 5.9 |
| Attack Vector | Network | N/A | Network |
| Attack Complexity | High | N/A | High |
| Privileges Required | None | N/A | None |
| User Interaction | None | N/A | None |
| Scope | Unchanged | N/A | Unchanged |
| Confidentiality | High | N/A | High |
| Integrity Impact | None | N/A | None |
| Availability Impact | None | N/A | None |
Vector
Red Hat: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
cve.org: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
Understanding the Weakness (CWE)
Confidentiality
Technical Impact: Read Application Data
Data can "bleed" from one session to another through member variables of singleton objects, such as Servlets, and objects from a shared pool. Storing user data in Servlet member fields introduces a data access race condition.
Frequently Asked Questions
Not sure what something means? Check out our Security Glossary.
Want to get errata notifications? Sign up here.
