CVE-2026-85296— Apache Camel AS2 组件密钥混淆漏洞
一分钟漏洞结论
影响对象
Apache Software Foundation Apache Camel
利用判断
尚无明确在野利用证据，仍需结合暴露面评估
建议动作
优先检查厂商安全公告和参考链接中的修复版本；无法立即升级时，限制受影响服务暴露并加强监测。
Apache Camel AS2 组件存在“数据元素暴露至错误会话”漏洞。 受影响版本：Apache Camel 4.0.0 至 4.18.5（不含 4.18.5），以及 4.19.0 至 4.22.1（不含 4.22.1）。 该漏洞的成因在于：属于单个请求的签名材料被存储在跨请求共享的状态中，而非局限于当前正在处理的请求。当部署环境服务多个交易伙伴时，并发或连续到达的请求可能相互观察到彼此的签名材料，导致消息处置通知（MDN）被错误地用其他交易伙伴的私钥进行签名。其后果是引发“跨伙伴密钥混淆”：接收回执被错误归因
可能的 ATT&CK 技术 1 AI
T1190 · Exploit Public-Facing Application
获取后续新漏洞提醒
登录后订阅
一、 漏洞 CVE-2026-85296 基础信息
漏洞信息
对漏洞内容有疑问？看看神龙的深度分析是否有帮助！
查看神龙十问 ↗
尽管我们使用了先进的大模型技术，但其输出仍可能包含不准确或过时的信息。神龙努力确保数据的准确性，但请您根据实际情况进行核实和判断。
Vulnerability Title
Apache Camel: Camel-AS2 Cross-Partner Signing Key Confusion via Shared Per-Request State
来源: CVE Program / CVE List V5
Vulnerability Description
Exposure of Data Element to Wrong Session vulnerability in Apache Camel AS2 component.
This issue affects Apache Camel: from 4.0.0 before 4.18.5, from 4.19.0 before 4.22.1.
Signing material belonging to an individual request was stored in state that is shared across requests rather than confined to the request being processed. Where a deployment serves more than one trading partner, concurrent or successive requests could therefore observe each other's material, and a Message Disposition Notification could be signed with the key of a partner other than the one the receipt was for. The result is cross-partner key confusion: a receipt attributable to the wrong partner, and one partner's signing material used while handling another partner's exchange. AS2 deployments are typically multi-partner by design, so the condition is reached by ordinary concurrent traffic rather than by anything the attacker must arrange.
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. Per-request signing keys are now confined to the request being processed in ResponseMDN. For deployments that cannot upgrade immediately, run a separate Camel context per trading partner so that no signing material is shared between them.
来源: CVE Program / CVE List V5
CVSS Information
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:L/A:N
来源: CVE Program / CVE List V5
Vulnerability Type
对错误会话暴露数据元素
来源: CVE Program / CVE List V5
受影响产品
| 厂商 | 产品 | 影响版本 | CPE | 订阅 |
|---|---|---|---|---|
| Apache Software Foundation | Apache Camel | 4.0.0 ~ 4.18.5 | - |
|
二、漏洞 CVE-2026-85296 的公开POC
| # | POC 描述 | 源链接 | 神龙链接 |
|---|
AI 生成 POC
高级
未找到公开 POC。
登录以生成 AI POC三、漏洞 CVE-2026-85296 的情报信息
请登录查看更多情报信息。
CVE-2026-85296 补丁与修复 (3)
CVE-2026-85296 厂商安全公告 (2)
-
-
🔗 Apache Camel Security Advisory - CVE-2026-85296 - Apache Camel vendor-advisory
同批安全公告 · 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-78165 | 8.8 HIGH | Apache Camel 反序列化漏洞 |
| CVE-2026-80312 | 8.2 HIGH | Apache Camel OAuth 身份验证绕过漏洞 |
| CVE-2026-80344 | 8.2 HIGH | Apache Camel 服务端请求伪造及凭证泄露漏洞 |
| CVE-2026-80343 | 8.2 HIGH | Apache Camel Netty-HTTP 路径匹配绕过漏洞 |
| CVE-2026-78164 | 8.2 HIGH | Apache Camel HTTP 生产者远程代码执行漏洞 |
| CVE-2026-88901 | 8.2 HIGH | Apache Camel 默认解析外部实体漏洞 |
| CVE-2026-85251 | 7.5 HIGH | Apache Camel HTTP 凭据泄露漏洞 |
| CVE-2026-85250 | 7.5 HIGH | Apache Camel XPath XML外部实体及文件泄露漏洞 |
| 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-85314 | 6.5 MEDIUM | Apache Camel 邮件头注入漏洞 |
| CVE-2026-85249 | 6.5 MEDIUM | Apache Camel 未过滤元数据导致头部注入漏洞 |
| CVE-2026-85254 | 6.5 MEDIUM | Apache Camel 请求头回显抑制绕过漏洞 |
显示前 20 条，共 62 条。 查看全部 → →
IV. Related Vulnerabilities
V. Comments for CVE-2026-85296
暂无评论