CVE-2026-94386— Apache Camel OAuth 跨作用域令牌重用漏洞
一分钟漏洞结论
影响对象
Apache Software Foundation Apache Camel
利用判断
尚无明确在野利用证据，仍需结合暴露面评估
建议动作
优先检查厂商安全公告和参考链接中的修复版本；无法立即升级时，限制受影响服务暴露并加强监测。
Apache Camel OAuth 组件中存在“缓存包含敏感信息”的漏洞。 该问题影响 Apache Camel 版本范围：从 4.19.0 起，直至 4.22.2 之前的版本。 OAuthClientCredentialsTokenResolver 通过客户端凭证授权（client credentials grant）为组件获取 OAuth 2.0 访问令牌（bearer token），这些组件使用命名 OAuth 配置文件对其出站调用进行身份验证，例如 camel-openai、camel-langchain
影响版本矩阵 1
| 厂商 | 产品 | 版本范围 | 状态 |
|---|---|---|---|
| Apache Software Foundation | Apache Camel | 4.19.0< 4.22.2 |
affected |
获取后续新漏洞提醒
登录后订阅
一、 漏洞 CVE-2026-94386 基础信息
漏洞信息
对漏洞内容有疑问？看看神龙的深度分析是否有帮助！
查看神龙十问 ↗
尽管我们使用了先进的大模型技术，但其输出仍可能包含不准确或过时的信息。神龙努力确保数据的准确性，但请您根据实际情况进行核实和判断。
Vulnerability Title
Apache Camel: Camel-OAuth Cross-Scope Token Reuse via an Under-Keyed JVM-Global Client Credentials Token Cache
来源: CVE Program / CVE List V5
Vulnerability Description
Use of Cache Containing Sensitive Information vulnerability in Apache Camel Oauth component.
This issue affects Apache Camel: from 4.19.0 before 4.22.2.
OAuthClientCredentialsTokenResolver obtains OAuth 2.0 bearer tokens through the client credentials grant on behalf of the components that authenticate their outbound calls with a named OAuth profile, such as camel-openai, camel-langchain4j-agent, camel-huggingface, camel-docling, camel-a2a, camel-spring-ai-chat and the IBM watsonx components, and of applications that call the OAuthClientAuthenticationFactory SPI directly. It kept the tokens it obtained in a static cache shared by every resolver instance and every CamelContext in the JVM, and keyed that cache on the token endpoint and the client ID only, although the token request also carries the client secret and the requested scope. Two profiles that share a token endpoint and a client ID but request different scopes, or authenticate with different client secrets, therefore mapped to the same cache entry: the profile that resolved a token first populated the entry, and the other profile was then handed that token, with no token request made under its own configuration, for as long as the token remained valid. Token caching is enabled by default, and pointing several profiles at one identity provider client is an ordinary use of the profile support rather than an opt-in to an insecure setting. The outcome is an outbound request that carries a token issued for another profile's scope, which can grant broader authority than the calling profile was configured for, or reach a service the token was not issued for; with identity providers that derive a token's audience from the requested scope, a different scope can mean a token for a different service altogether. A profile configured with a different client secret was likewise served the token obtained with the other secret, without authenticating with its own. The profiles are configured by the deployment, which is trusted, so no untrusted input reaches the cache: the party that gains is the service that receives a token it was not meant to receive, which, if hostile or compromised, can replay that token within its scope. Reaching the issue requires a deployment that defines more than one profile sharing a token endpoint and client ID while differing in scope or client secret.
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.2. The 4.19.x to 4.21.x release lines reached end of life before this issue was resolved and will not receive a fix, so deployments on them must move to a supported release. For deployments that cannot upgrade immediately, disable token caching on every OAuth profile that shares a token endpoint and client ID with another profile, by setting camel.oauth.NAME.cache-tokens=false for a named profile or camel.oauth.cache-tokens=false for the default one, so that each resolution requests a token with that profile’s own scope and client secret, at the cost of a token request on every resolution. Alternatively, register a separate client at the identity provider for each profile that needs a different scope or client secret, so that no two such profiles share a client ID.
来源: CVE Program / CVE List V5
CVSS Information
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N
来源: CVE Program / CVE List V5
Vulnerability Type
通过缓存导致的信息暴露
来源: CVE Program / CVE List V5
受影响产品
| 厂商 | 产品 | 影响版本 | CPE | 订阅 |
|---|---|---|---|---|
| Apache Software Foundation | Apache Camel | 4.19.0 ~ 4.22.2 | - |
|
二、漏洞 CVE-2026-94386 的公开POC
| # | POC 描述 | 源链接 | 神龙链接 |
|---|
AI 生成 POC
高级
未找到公开 POC。
登录以生成 AI POC三、漏洞 CVE-2026-94386 的情报信息
请登录查看更多情报信息。
CVE-2026-94386 补丁与修复 (2)
CVE-2026-94386 厂商安全公告 (2)
同批安全公告 · Apache Software Foundation · 2026-10-26 · 共 12 条
| CVE-2026-115748 | 8.8 HIGH | Apache Vysper 未授权访问漏洞 |
| CVE-2026-115721 | 7.5 HIGH | Apache Vysper 无界分配漏洞 |
| CVE-2026-90885 | 7.5 HIGH | Apache Camel 任意版本 XXE 漏洞 |
| CVE-2026-95628 | 5.4 MEDIUM | Apache Camel 路径验证绕过漏洞 |
| CVE-2026-95629 | 5.4 MEDIUM | Apache Camel 任意目录写入漏洞 |
| CVE-2026-95664 | 5.4 MEDIUM | Apache Camel 远程代码执行漏洞 |
| CVE-2026-101259 | 5.3 MEDIUM | Apache Camel CoAP 组件信息泄露漏洞 |
| CVE-2026-95663 | 4.8 MEDIUM | Apache Camel 远程代码执行漏洞 |
| CVE-2026-111422 | Apache Airflow SSH 远程代码执行漏洞 | |
| CVE-2026-110748 | Apache SIS 路径限制不当漏洞 | |
| CVE-2026-110733 | Apache SIS SQL 特性存储未验证排序表达式 SQL 注入漏洞 |