Severity:
CVSS 3.1: 5.9 (medium) CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
Affected versions:
- Apache Camel (org.apache.camel:camel-thrift) 4.0.0 before 4.18.5
- Apache Camel (org.apache.camel:camel-thrift) 4.19.0 before 4.22.1
- Apache Camel (org.apache.camel:camel-thrift) 4.18.5 unaffected
- Apache Camel (org.apache.camel:camel-thrift) 4.22.1 unaffected
- Apache Camel (org.apache.camel:camel-thrift) 4.23.0 unaffected
Description:
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.
Solution:
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.
Work Arounds:
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.
Credit:
Claude Security (finder)
Andrea Cosentino (remediation developer)
References:
https://camel.apache.org/security/CVE-2026-85245.html
https://issues.apache.org/jira/browse/CAMEL-24442
https://github.com/apache/camel/pull/25823
https://github.com/apache/camel/pull/25940
https://github.com/apache/camel/pull/25942
https://camel.apache.org/
https://www.cve.org/CVERecord?id=CVE-2026-85245
