---
id: CVE-2026-85245
title: >-
  Apache Camel: Camel-Thrift Cross-Exchange Data Disclosure via a Shared
  Deserialization Target
summary: >-
  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 th…
severity: medium
cvss: 5.9
cvssVector: 'CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N'
cvssSource: cna
cwe:
  - CWE-488
vendor: Apache Software Foundation
product: 'org.apache.camel:camel-thrift'
affected:
  - 'org.apache.camel:camel-thrift >= 4.0.0 < 4.18.5'
  - 'org.apache.camel:camel-thrift >= 4.19.0 < 4.22.1'
published: '2026-10-19'
updated: '2026-10-19'
sourceUpdated: '2026-10-19T10:32:44.450Z'
source: CVEORG
sourceUrl: 'https://www.cve.org/CVERecord?id=CVE-2026-85245'
references:
  - url: 'https://camel.apache.org/security/CVE-2026-85245.html'
    label: Apache Camel Security Advisory - CVE-2026-85245
  - url: 'https://issues.apache.org/jira/browse/CAMEL-24442'
    label: CAMEL-24442
  - url: 'https://github.com/apache/camel/pull/25823'
    label: >-
      Fix on main, released in 4.23.0 (commit
      c52d3cfa1c343a49261d77a5213dba92244a38f6)
  - url: 'https://github.com/apache/camel/pull/25940'
    label: >-
      Backport to camel-4.22.x, released in 4.22.1 (commit
      260989268cbc6d258b1fcba63770be8ebbec40cb)
  - url: 'https://github.com/apache/camel/pull/25942'
    label: >-
      Backport to camel-4.18.x, released in 4.18.5 (commit
      af1efbcccf5882b1ef0094db718972da3190e7e9)
tags:
  - cve.org
ingestedAt: '2026-10-19T12:27:23.816Z'
---

## Overview

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

- `org.apache.camel:camel-thrift >= 4.0.0 < 4.18.5`
- `org.apache.camel:camel-thrift >= 4.19.0 < 4.22.1`

## Remediation

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.

### Workarounds

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.