CVE-2026-78165— Apache Camel 反序列化漏洞
一分钟漏洞结论
影响对象
Apache Software Foundation Apache Camel
利用判断
尚无明确在野利用证据，仍需结合暴露面评估
建议动作
优先检查厂商安全公告和参考链接中的修复版本；无法立即升级时，限制受影响服务暴露并加强监测。
Apache Camel Spring Redis 组件存在“反序列化不可信数据”漏洞。 受影响版本范围： Apache Camel 2.11.0 至 4.18.4（含） Apache Camel 4.19.0 至 4.22.0（含） 漏洞详情： 方法在用户未配置序列化器选项时，会惰性构建一个裸 实例，并将该实例用于组件执行的所有读取操作。Spring 的实现通过 委托至 ，后者使用 读取字节流，但未在流上安装 。因此，任意序列化类图均可被实例化，并触发其 方法。 在构建 对象之前，即对订阅通道中每条消息的原始字节
获取后续新漏洞提醒
登录后订阅
一、 漏洞 CVE-2026-78165 基础信息
漏洞信息
对漏洞内容有疑问？看看神龙的深度分析是否有帮助！
查看神龙十问 ↗
尽管我们使用了先进的大模型技术，但其输出仍可能包含不准确或过时的信息。神龙努力确保数据的准确性，但请您根据实际情况进行核实和判断。
Vulnerability Title
Apache Camel: Camel-Spring-Redis Unfiltered Java Deserialization of Redis Payloads
来源: CVE Program / CVE List V5
Vulnerability Description
Deserialization of Untrusted Data vulnerability in Apache Camel Spring Redis component.
This issue affects Apache Camel: from 2.11.0 before 4.18.5, from 4.19.0 before 4.22.1.
RedisConfiguration.getSerializer lazily built a bare JdkSerializationRedisSerializer whenever no serializer option was configured, and that instance was used for every read the component performs. Spring's implementation delegates through DeserializingConverter to DefaultDeserializer, which reads the bytes with a ConfigurableObjectInputStream and installs no java.io.ObjectInputFilter on the stream, so an arbitrary serialized class graph was materialised and its readObject method executed. RedisConsumer.setBody applied that serializer to the raw bytes of every message published to the subscribed channels, before the Exchange was constructed and therefore before any route logic could inspect the message, so an actor able to issue PUBLISH on a subscribed channel reached the deserialization sink directly. The same default serializer backed the RedisTemplate built by RedisConfiguration.createDefaultTemplate, so the producer read commands GET, HGET, HGETALL and HVALS deserialized whatever was stored in the Redis keyspace, and SpringRedisIdempotentRepository shared that template. Configuring a custom redisTemplate did not close the consumer path, because RedisConsumer.setBody reads getSerializer directly rather than the serializer attached to the template, so a deployment that had wired a String serializer into its own template remained exposed on the consumer side unless it also set the serializer option. The component never constructed a java.io.ObjectInputStream itself, which is why earlier passes over the Camel codebase for unfiltered Java deserialization did not reach it. The behaviour dates back to the introduction of the component, first released in 2.11.0, and was unchanged until this fix.
Users are recommended to upgrade to version 4.23.0, which fixes the issue. If users are on the 4.22.x releases stream, then they are suggested to upgrade to 4.22.1. If users are on the 4.18.x releases stream, then they are suggested to upgrade to 4.18.5. The 4.14.x releases stream and earlier reached end of life before this issue was resolved and will not receive a fix, so deployments on those lines must move to a supported release. For deployments that cannot upgrade immediately, set the JVM-wide jdk.serialFilter system property, which the affected code path honours because it reads through a java.io.ObjectInputStream, for example -Djdk.serialFilter=!java.net.**;java.**;javax.**;org.apache.camel.**;!* ; or set the serializer endpoint option to a serializer that does not use Java serialization, such as StringRedisSerializer, noting that this must be set as the serializer option and not only on a custom redisTemplate. As defence in depth, require authentication on the Redis instance and restrict which clients may publish to the subscribed channels, and do not expose a Redis instance consumed by Camel to untrusted networks.
来源: CVE Program / CVE List V5
CVSS Information
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
来源: CVE Program / CVE List V5
Vulnerability Type
可信数据的反序列化
来源: CVE Program / CVE List V5
受影响产品
| 厂商 | 产品 | 影响版本 | CPE | 订阅 |
|---|---|---|---|---|
| Apache Software Foundation | Apache Camel | 2.11.0 ~ 4.18.5 | - |
|
二、漏洞 CVE-2026-78165 的公开POC
| # | POC 描述 | 源链接 | 神龙链接 |
|---|
AI 生成 POC
高级
未找到公开 POC。
登录以生成 AI POC三、漏洞 CVE-2026-78165 的情报信息
请登录查看更多情报信息。
CVE-2026-78165 补丁与修复 (5)
CVE-2026-78165 厂商安全公告 (1)
同批安全公告 · Apache Software Foundation · 2026-10-19 · 共 62 条
| CVE-2026-78162 | 10.0 CRITICAL | Apache Camel 反序列化过滤缺失漏洞 |
| CVE-2026-88900 | 8.8 HIGH | Apache Camel 反序列化漏洞 |
| CVE-2026-83531 | 8.8 HIGH | Apache Camel 动态路由控制端点远程代码执行漏洞 |
| CVE-2026-80343 | 8.2 HIGH | Apache Camel Netty-HTTP 路径匹配绕过漏洞 |
| CVE-2026-80344 | 8.2 HIGH | Apache Camel 服务端请求伪造及凭证泄露漏洞 |
| CVE-2026-80312 | 8.2 HIGH | Apache Camel OAuth 身份验证绕过漏洞 |
| CVE-2026-78164 | 8.2 HIGH | Apache Camel HTTP 生产者远程代码执行漏洞 |
| CVE-2026-88901 | 8.2 HIGH | Apache Camel 默认解析外部实体漏洞 |
| CVE-2026-85250 | 7.5 HIGH | Apache Camel XPath XML外部实体及文件泄露漏洞 |
| CVE-2026-85251 | 7.5 HIGH | Apache Camel HTTP 凭据泄露漏洞 |
| CVE-2026-79984 | 7.4 HIGH | Apache Camel 远程代码执行漏洞 |
| CVE-2026-79985 | 7.4 HIGH | Apache Camel 远程文件读取漏洞 |
| CVE-2026-79986 | 7.4 HIGH | Apache Camel 远程文件读取漏洞 |
| CVE-2026-79983 | 7.4 HIGH | Apache Camel 远程文件读取漏洞 |
| CVE-2026-91858 | 6.5 MEDIUM | Apache Camel Camel-FOP 远程代码执行漏洞 |
| CVE-2026-84176 | 6.5 MEDIUM | Apache Camel 跨域凭证暴露漏洞 |
| CVE-2026-85249 | 6.5 MEDIUM | Apache Camel 未过滤元数据导致头部注入漏洞 |
| CVE-2026-85254 | 6.5 MEDIUM | Apache Camel 请求头回显抑制绕过漏洞 |
| CVE-2026-85296 | 6.5 MEDIUM | Apache Camel AS2 组件密钥混淆漏洞 |
| CVE-2026-85314 | 6.5 MEDIUM | Apache Camel 邮件头注入漏洞 |
显示前 20 条，共 62 条。 查看全部 → →
IV. Related Vulnerabilities
V. Comments for CVE-2026-78165
暂无评论