Camel-Thrift (4.0.0-4.18.4, 4.19.0-4.22.0) - CraftedSignal Threat Feedhttps://feed.craftedsignal.io/products/camel-thrift-4.0.0-4.18.4-4.19.0-4.22.0/Trending threats, MITRE ATT&CK coverage, and detection metadata. Fed continuously.Hugoenhello@craftedsignal.iohello@craftedsignal.ioMon, 19 Oct 2026 12:17:15 +0000https://feed.craftedsignal.io/favicon-32x32.pngCraftedSignal Threat Feedhttps://feed.craftedsignal.io/3232https://feed.craftedsignal.io/favicon.svgCross-Exchange Data Disclosure in Apache Camel Thrift Componenthttps://feed.craftedsignal.io/briefs/2026-10-camel-thrift-data-disclosure/Mon, 19 Oct 2026 12:17:15 +0000hello@craftedsignal.iohttps://feed.craftedsignal.io/briefs/2026-10-camel-thrift-data-disclosure/A vulnerability in the camel-thrift component, CVE-2026-85245, allows cross-tenant data disclosure by reusing a shared object instance for unmarshalling Thrift payloads.Apache Camel’s camel-thrift component is vulnerable to a cross-exchange data disclosure flaw identified as CVE-2026-85245. The vulnerability resides in ThriftDataFormat.unmarshal, which deserializes incoming data into a shared defaultInstance rather than creating a fresh object per exchange. Because this instance is process-wide, fields absent from a subsequent Thrift payload retain values from previous messages. In multi-tenant or shared-route environments, this results in data leakage where one user or tenant may inadvertently read sensitive data belonging to another user. This issue affects Apache Camel versions 4.0.0 through 4.18.4 and 4.19.0 through 4.22.0. The vulnerability is mitigated in versions 4.18.5, 4.22.1, and 4.23.0, where the implementation ensures a deep copy of the defaultInstance is created for every exchange.

Impact

Successful exploitation leads to unauthorized access to sensitive data across different sessions or tenants sharing the same Camel route. This impacts multi-tenant applications using Apache Camel for Thrift-based data processing, potentially exposing PII, credentials, or other private payload content that persists in the shared object instance across concurrent or sequential exchanges.

Recommendation

  1. Upgrade Apache Camel deployments to versions 4.18.5, 4.22.1, or 4.23.0 to incorporate the fix for CVE-2026-85245.
  2. If patching is not immediately feasible, modify application code to manually copy the unmarshalled body into a new instance immediately after the data format operation and ensure no references to the returned shared object are retained.
]]>mediumadvisorydata-disclosureapache-camelcve-2026-85245