Goal Reached Thanks to every supporter — we hit 100%!

Goal: 1000 CNY · Raised: 1359 CNY

100%

CVE-2026-85245— Apache Camel: Camel-Thrift Cross-Exchange Data Disclosure via a Shared Deserialization Target

Quick assessment

Affected
Apache Software Foundation Apache Camel
Exploitation
No confirmed in-the-wild exploitation; assess based on exposure
Recommended action
Check the vendor advisory and references for a fixed version. If immediate upgrade is impossible, restrict exposure and increase monitoring.

Apache Camel Thrift 组件存在“数据元素暴露至错误会话”的漏洞。 受影响版本:Apache Camel 4.0.0 至 4.18.4,以及 4.19.0 至 4.22.0。 问题根源在于,Thrift 数据格式在反序列化(unmarshal)传入数据时,并未创建新的目标类型实例,而是将数据写入共享的默认实例(defaultInstance),并将该共享对象作为消息交换体(exchange body)返回。由于该实例在整个进程中共享,在反序列化某条消息时写入的状态会保留在对象中,并被后续使用相同类型

CVSS 5.9 · Medium

Possible ATT&CK Techniques 1 AI

T1082 · System Information Discovery

Affected Version Matrix 5

VendorProduct Version RangeStatus
Apache Software Foundation Apache Camel 4.0.0< 4.18.5 affected
4.19.0< 4.22.1 affected
4.18.5 unaffected
4.22.1 unaffected
4.23.0 unaffected
Get alerts for future matching vulnerabilities Log in to subscribe

I. Basic Information for CVE-2026-85245

Vulnerability Information

Have questions about the vulnerability? See if Shenlong's analysis helps!
View Shenlong Deep Dive ↗

Although we use advanced large model technology, its output may still contain inaccurate or outdated information.Shenlong tries to ensure data accuracy, but please verify and judge based on the actual situation.

Vulnerability Title
Apache Camel: Camel-Thrift Cross-Exchange Data Disclosure via a Shared Deserialization Target
Source: CVE Program / CVE List V5
Vulnerability 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.
Source: CVE Program / CVE List V5
CVSS Information
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
Source: CVE Program / CVE List V5
Vulnerability Type
对错误会话暴露数据元素
Source: CVE Program / CVE List V5

Affected Products

Vendor Product Affected Versions CPE Subscribe
Apache Software Foundation Apache Camel 4.0.0 ~ 4.18.5 -

II. Public POCs for CVE-2026-85245

# POC Description Source Link Shenlong Link
AI-Generated POC Premium

No public POC found.

Login to generate AI POC

III. Intelligence Information for CVE-2026-85245

请登录查看更多情报信息。

Patches & Fixes for CVE-2026-85245 (3)

Vendor Advisories for CVE-2026-85245 (1)

Vendor Pages for CVE-2026-85245 (1)

Same Patch Batch · Apache Software Foundation · 2026-10-19 · 62 CVEs total

CVE-2026-78162 10.0 CRITICAL Apache Camel: Camel-Hazelcast Managed Instances Missing Java Deserialization Filter (Incom
CVE-2026-88900 8.8 HIGH Apache Camel: Camel-JGroups: Unsafe Java Deserialization of Cluster Messages in the JGroup
CVE-2026-83531 8.8 HIGH Apache Camel: Camel-Dynamic-Router Control Endpoint Compiles Predicate Expressions Supplie
CVE-2026-78165 8.8 HIGH Apache Camel: Camel-Spring-Redis Unfiltered Java Deserialization of Redis Payloads
CVE-2026-80312 8.2 HIGH Apache Camel: Camel-OAuth Authentication Bypass via Fail-Open Processors
CVE-2026-80344 8.2 HIGH Apache Camel: Camel-AS2 Server-Side Request Forgery and Credential Disclosure via Asynchro
CVE-2026-80343 8.2 HIGH Apache Camel: Camel-Netty-HTTP Security Constraint Bypass via Case-Sensitive Context-Path
CVE-2026-78164 8.2 HIGH Apache Camel: HTTP producers resolve property placeholders in message-supplied URI overrid
CVE-2026-88901 8.2 HIGH Apache Camel: Camel-Smooks XML External Entity Processing, external entities resolved by d
CVE-2026-85251 7.5 HIGH Apache Camel: Camel-HTTP Credential Disclosure to Cross-Host Redirect Targets
CVE-2026-85250 7.5 HIGH Apache Camel: Camel-XPath XML External Entity Processing and File Disclosure via the docum
CVE-2026-79984 7.4 HIGH Apache Camel: camel-mina-sftp resolved the remote path of a polled file from the name repo
CVE-2026-79985 7.4 HIGH Apache Camel: camel-smb resolved the remote path of a polled file from the name reported i
CVE-2026-79986 7.4 HIGH Apache Camel: camel-azure-files resolved the remote path of a polled file from the name re
CVE-2026-79983 7.4 HIGH Apache Camel: camel-ftp resolved the remote path of a polled file from the name reported i
CVE-2026-91858 6.5 MEDIUM Apache Camel: Camel-FOP Resolves External DTDs and Entities From Untrusted XSL-FO Input Wh
CVE-2026-84176 6.5 MEDIUM Apache Camel: Camel-Platform-HTTP-Vertx Cross-Origin Credential Exposure via Wildcard Orig
CVE-2026-85249 6.5 MEDIUM Apache Camel: Camel-Tika Header Injection via Unfiltered Document Metadata
CVE-2026-85314 6.5 MEDIUM Apache Camel: Camel-Mail Header Injection via Unfiltered mail.smtp Headers in the MimeMult
CVE-2026-85296 6.5 MEDIUM Apache Camel: Camel-AS2 Cross-Partner Signing Key Confusion via Shared Per-Request State

Showing top 20 of 62 CVEs. View all on vendor page &rarr; →

IV. Related Vulnerabilities

V. Comments for CVE-2026-85245

No comments yet


Leave a comment