目标达成 感谢每一位支持者 — 我们达成了 100% 目标!

目标: 1000 元 · 已筹: 1359 元

100%

CVE-2026-83531— Apache Camel 动态路由控制端点远程代码执行漏洞

一分钟漏洞结论

影响对象
Apache Software Foundation Apache Camel
利用判断
尚无明确在野利用证据,仍需结合暴露面评估
建议动作
优先检查厂商安全公告和参考链接中的修复版本;无法立即升级时,限制受影响服务暴露并加强监测。

Apache Camel 中存在“代码生成控制不当”(代码注入)以及“表达式语言语句中特殊元素中和不当”(表达式语言注入)漏洞。 受影响版本范围: Apache Camel 4.4.0 至 4.18.5(不含 4.18.5) Apache Camel 4.19.0 至 4.22.1(不含 4.22.1) 漏洞详情: 自 4.4.0 版本引入的 端点允许路由参与者通过发送控制消息来管理动态路由器的订阅。在处理订阅或更新请求时, 会从传入消息中获取用于编译的订阅谓词(predicate)及其所使用的语言名称。这些参数可

CVSS 8.8 · High
获取后续新漏洞提醒 登录后订阅

一、 漏洞 CVE-2026-83531 基础信息

漏洞信息

对漏洞内容有疑问?看看神龙的深度分析是否有帮助!
查看神龙十问 ↗

尽管我们使用了先进的大模型技术,但其输出仍可能包含不准确或过时的信息。神龙努力确保数据的准确性,但请您根据实际情况进行核实和判断。

Vulnerability Title
Apache Camel: Camel-Dynamic-Router Control Endpoint Compiles Predicate Expressions Supplied by Control Messages
来源: CVE Program / CVE List V5
Vulnerability Description
Improper Control of Generation of Code ('Code Injection'), Improper Neutralization of Special Elements used in an Expression Language Statement ('Expression Language Injection') vulnerability in Apache Camel. This issue affects Apache Camel: from 4.4.0 before 4.18.5, from 4.19.0 before 4.22.1. The dynamic-router-control endpoint, introduced in 4.4.0, lets routing participants manage Dynamic Router subscriptions by sending control messages. When it handled a subscribe or update request, DynamicRouterControlProducer took the subscription predicate and the name of the language used to compile it from the incoming message, either from the predicate and expressionLanguage fields of a DynamicRouterControlMessage body or from the CamelDynamicRouterPredicate and CamelDynamicRouterExpressionLanguage headers. DynamicRouterControlService then resolved that language from the CamelContext and compiled the expression into a Predicate, with no allow-list and no opt-in. The compiled predicate was added to the channel's rule base and evaluated against every exchange routed through the corresponding dynamic-router endpoint for as long as the subscription existed. A route that forwards messages from an external transport to the control endpoint, as shown in the component documentation for routing participants in other JVMs or applications, therefore let any actor able to send a message on that transport supply an expression of their choosing, which was evaluated with the privileges of the Camel process. Any expression language available on the classpath could be selected, including the simple language, which is always present and was the default on the header path, so removing optional expression languages from the classpath did not prevent the issue. Exploitation requires the ability to send a message on a transport whose route forwards it to a dynamic-router-control endpoint; no other authentication or user interaction is needed. Releases before 4.4.0 are not affected, because their control channel took predicate expressions only from the endpoint URI configured by the route author. 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. After upgrading, a control message that carries a predicate expression or an expression language is rejected unless the new allowPredicateFromMessage option is enabled on the dynamic-router-control endpoint; enable it only when every sender of control messages is trusted. For deployments that cannot upgrade immediately, do not forward messages from untrusted or shared transports to a dynamic-router-control endpoint. Where control messages must cross such a transport, authenticate the sender and make sure the predicate and expression language of each subscription are set by the route rather than taken from the incoming message, for example by removing the CamelDynamicRouterPredicate and CamelDynamicRouterExpressionLanguage headers and clearing the predicate and expressionLanguage fields of a DynamicRouterControlMessage before it reaches the endpoint. Removing optional expression languages from the classpath is not a sufficient workaround. As defence in depth, restrict who can send to the transports that feed the control endpoint, and on 4.23.0 and 4.22.1 set the allowedSchemes option of the dynamic-router endpoint to limit which endpoints a subscription's destinationUri may name.
来源: 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 4.4.0 ~ 4.18.5 -

二、漏洞 CVE-2026-83531 的公开POC

# POC 描述 源链接 神龙链接
AI 生成 POC 高级

未找到公开 POC。

登录以生成 AI POC

三、漏洞 CVE-2026-83531 的情报信息

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

CVE-2026-83531 其他参考 (6)

同批安全公告 · 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-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-85250 7.5 HIGH Apache Camel XPath XML外部实体及文件泄露漏洞
CVE-2026-85251 7.5 HIGH Apache Camel HTTP 凭据泄露漏洞
CVE-2026-79983 7.4 HIGH Apache Camel 远程文件读取漏洞
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-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-83531

暂无评论


发表评论