---
id: "CVE-2026-85245"
kind: "vulnerability"
aliases: ["CVE-2026-85245"]
title: "Apache Camel Thrift: shared instance leaks one message's data to others"
severity: "medium"
cvss: 5.9
epss: null
exploited: false
status: "open"
category: "package"
products: []
ecosystems: []
tags: ["apache-camel", "java", "multi-tenant", "package", "thrift"]
not_affected_if: ["no-thrift-data-format", "single-tenant"]
published_at: "2026-10-19T11:17:22+00:00"
first_seen_at: "2026-10-23T21:57:18+00:00"
updated_at: "2026-10-25T04:08:48+00:00"
sources: [{"source": "nvd", "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-85245", "first_seen_at": "2026-10-23T21:57:18+00:00"}]
---

# Apache Camel Thrift: shared instance leaks one message's data to others

The Thrift data format in Apache Camel unmarshals every message into one shared process-wide object instead of a fresh copy. Fields left out of a later payload keep the previous message's values, so one sender's data can be read while another sender's message is processed.

_Summary, check and fix written by a model from the sources; labelled as such._

## How to check

- Check the Apache Camel version in the project build file (for example `camel-bom` or `camel-thrift` version); affected are `4.0.0` before `4.18.5` and `4.19.0` before `4.22.1`
- Look for routes that use the Thrift data format (`unmarshal().thrift(...)`) and serve more than one tenant or user through the same route

## Fix

- Upgrade Apache Camel to `4.23.0`; on the LTS streams move to `4.18.5` (4.18.x) or `4.22.1` (4.22.x)
- If an upgrade is not possible yet, copy the unmarshalled body into a new instance right after the Thrift data format runs and do not keep references to the returned object

## Timeline

- 2026-10-23T21:57:18+00:00 nvd https://nvd.nist.gov/vuln/detail/CVE-2026-85245

## From the sources

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.

---

_Free to read at a human pace. An API with keys and an MCP server are in preparation; early access: hello@infrastack.ai_