CVE-2026-85245: Apache Camel: Camel-Thrift Cross-Exchange Data Disclosure via a Shared Deserialization Target
Exposure of Data Element to Wrong Session vulnerability in Apache Camel Thrift component.
This issue affects Apache Camel: from 4.0.0 before 4.18.5, from 4.19.0 before 4.22.1.
The Thrift data format unmarshalled incoming data into the shared defaultInstance of the target type rather than into a fresh copy, and returned that shared object as the exchange body. Because the instance is shared process-wide, state written while unmarshalling one message stayed on the object and was visible to every later message that used the same type. Fields absent from a later payload retained the previous message's values, so content belonging to one sender could be read while processing another sender's message, and concurrent exchanges could observe each other's partially written state. In a deployment that serves more than one tenant or user through the same route, that is disclosure of one party's data to another.
Upgrade to Apache Camel 4.23.0, which fixes the issue. Users on the 4.18.x LTS releases stream should upgrade to 4.18.5. Users on the 4.22.x LTS releases stream should upgrade to 4.22.1. Unmarshalling now deserializes into a copy, so each exchange gets its own instance and no state carries between messages. For deployments that cannot upgrade immediately, copy the unmarshalled body into a new instance immediately after the data format runs, and do not retain references to the returned object.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
Apache Camelto a version that resolves this vulnerability.Fixed in 4.23.0 - Upgrade
Upgrade
Apache Camelto a version that resolves this vulnerability.Fixed in 4.18.5 - Upgrade
Upgrade
Apache Camelto a version that resolves this vulnerability.Fixed in 4.22.1 - Compensating control
For deployments that cannot upgrade immediately, copy the unmarshalled body into a new instance immediately after the data format runs, and do not retain references to the returned object.
Event History
Frequently Asked Questions
Which deployments are exposed to cross-user or cross-tenant disclosure?
Deployments that unmarshal Thrift messages through the affected Camel component and serve more than one tenant or user through the same route are exposed. Data from an earlier message can remain in fields omitted by a later message using the same target type.
What conditions are needed to exploit this issue?
An attacker needs to send a Thrift payload that is processed by an affected shared route and target type. Exploitation is network-accessible and requires no privileges or user interaction, but the attack complexity is rated high.
Are concurrent requests a concern?
Yes. Concurrent exchanges using the shared target instance can observe each other's partially written state, in addition to later messages retaining values from earlier payloads.
Which versions should be used to remediate the issue?
Upgrade to Apache Camel 4.23.0. For the LTS release streams, upgrade to 4.18.5 for 4.18.x or 4.22.1 for 4.22.x.