CVE-2026-79986— Apache Camel 远程文件读取漏洞
一分钟漏洞结论
影响对象
Apache Software Foundation Apache Camel
利用判断
尚无明确在野利用证据，仍需结合暴露面评估
建议动作
优先检查厂商安全公告和参考链接中的修复版本；无法立即升级时，限制受影响服务暴露并加强监测。
Apache Camel Azure Files 组件中存在“路径遍历”漏洞，即未能将路径名限制在受保护的目录内。 受影响版本范围： Apache Camel 4.0.0 至 4.18.4（即 4.0.0 之前版本，不含 4.18.5） Apache Camel 4.19.0 至 4.22.0（即 4.19.0 之前版本，不含 4.22.1） 漏洞原理： Camel 的远程文件消费者会轮询远程服务器上的指定目录，并通过将配置的目录路径与服务器目录列表中报告的文件名进行拼接，构建每个文件的绝对远程路径。该拼接操作（由
获取后续新漏洞提醒
登录后订阅
一、 漏洞 CVE-2026-79986 基础信息
漏洞信息
对漏洞内容有疑问？看看神龙的深度分析是否有帮助！
查看神龙十问 ↗
尽管我们使用了先进的大模型技术，但其输出仍可能包含不准确或过时的信息。神龙努力确保数据的准确性，但请您根据实际情况进行核实和判断。
Vulnerability Title
Apache Camel: camel-azure-files resolved the remote path of a polled file from the name reported in the server directory listing without constraining it to the directory being polled, so a listing entry containing traversal segments could be moved outside
来源: CVE Program / CVE List V5
Vulnerability Description
Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability in Apache Camel Azure Files component.
This issue affects Apache Camel: from 4.0.0 before 4.18.5, from 4.19.0 before 4.22.1.
The Camel remote-file consumers poll a directory on a remote server and build the absolute remote path of each file by concatenating the configured directory with the file name reported in the server's directory listing. That concatenation (FtpUtils.absoluteFilePath and GenericFileConsumer) applied no lexical normalization and no check that the result stayed inside the directory being polled, and the resulting path became the operand for every subsequent remote operation on the file: retrieval (FtpOperations.retrieveFile / SftpOperations, reached from GenericFileConsumer where the retrieve name is taken verbatim from GenericFile.getAbsoluteFilePath), deletion when delete=true (GenericFileDeleteProcessStrategy), and renaming when move, preMove, moveFailed or readLock=rename is configured (GenericFileProcessStrategySupport and GenericFileRenameExclusiveReadLockStrategy). Neither isValidFile nor isMatched performed any containment check. A listing entry that is not a single path segment therefore resolved to a path outside the configured polling directory, causing Camel to read, delete or rename files outside it using the endpoint's own credentials. A listing name is not route-controlled data. It is supplied by the remote server, and the FTP control channel carries no integrity protection at all, so an on-path attacker can rewrite a LIST response without holding any credentials; a compromised, malicious or multi-tenant server, or a server backed by a virtual filesystem, can emit such a name directly. Retrieval is reachable in a default consumer configuration, since the remote consumers download every listed file; deletion and renaming additionally require one of the disposition options above, all of which are common. Escape from the directory Camel was configured to poll is unconditional, while escape from the server's own account boundary additionally depends on whether that server confines the account. The jailStartingDirectory option, which is documented as restricting Camel to the starting directory and is enabled by default, governed producer writes and, since the localWorkDirectory containment work, consumer downloads to the local work directory - but it did not constrain this remote operand, so its name and description claimed a boundary that was not enforced here. The same entry point had already been recognised on the local side: the localWorkDirectory download path was constrained so that a remote file name containing parent-directory segments could not resolve outside the local work directory. The remote operand was the remaining half of that surface. This artifact provides the azure-files scheme. Its consumer derives from the same RemoteFileConsumer base class and composed the remote path through a plain concatenation helper, so it inherited the same unconstrained resolution. Reaching it requires a listing name that is not a single path segment, which the Azure Files REST service does not normally return; the exposure was corrected on the same basis as the other remote-file consumers rather than from a demonstrated proof of concept against this scheme.
Upgrade to Apache Camel 4.23.0, which fixes the issue. Users on the 4.22.x releases stream should upgrade to 4.22.1. Users on the 4.18.x LTS releases stream should upgrade to 4.18.5. The 4.14.x stream reached end of life and does not receive this fix; users on it should move to a supported releases stream.
来源: CVE Program / CVE List V5
CVSS Information
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/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-79986 的公开POC
| # | POC 描述 | 源链接 | 神龙链接 |
|---|
AI 生成 POC
高级
未找到公开 POC。
登录以生成 AI POC三、漏洞 CVE-2026-79986 的情报信息
请登录查看更多情报信息。
CVE-2026-79986 其他参考 (6)
-
https://issues.apache.org/jira/browse/CAMEL-24487 issue-tracking
-
https://camel.apache.org/security/CVE-2026-79986.html 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-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-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-79986
暂无评论