Live › vulnerability › CVE-2026-85245
Go to dashboardThe 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 written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-23 21:57 UTC. All times on this page are UTC.
Deployments that use the Camel Thrift data format on a route that carries data for more than one tenant or user through the same process. A single-tenant service where only one party's messages reach the route is much less exposed. Teams that do not use the Thrift component can skip it.
No product ranges from the sources yet.
camel-bom or camel-thrift version); affected are 4.0.0 before 4.18.5 and 4.19.0 before 4.22.1unmarshal().thrift(...)) and serve more than one tenant or user through the same route4.23.0; on the LTS streams move to 4.18.5 (4.18.x) or 4.22.1 (4.22.x)Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
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.
This page as .md · .json · in your agent: get_signal("CVE-2026-85245")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.