CVE-2026-40109— notification-controller 数据伪造问题漏洞
一分钟漏洞结论
影响对象
fluxcd notification-controller
利用判断
尚无明确在野利用证据，仍需结合暴露面评估
建议动作
优先检查厂商安全公告和参考链接中的修复版本；无法立即升级时，限制受影响服务暴露并加强监测。
notification-controller是Flux project开源的一个GitOps通知控制器。 notification-controller 1.8.3之前版本存在数据伪造问题漏洞，该漏洞源于未验证Google OIDC令牌的email声明，可能导致任何有效的Google签发令牌都能触发未经授权的Flux协调。
可能的 ATT&CK 技术 1 AI
T1190 · Exploit Public-Facing Application
获取后续新漏洞提醒
登录后订阅
一、 漏洞 CVE-2026-40109 基础信息
漏洞信息
对漏洞内容有疑问？看看神龙的深度分析是否有帮助！
查看神龙十问 ↗
尽管我们使用了先进的大模型技术，但其输出仍可能包含不准确或过时的信息。神龙努力确保数据的准确性，但请您根据实际情况进行核实和判断。
Vulnerability Title
Flux notification-controller GCR Receiver missing email validation allows unauthorized reconciliation triggering
来源: CVE Program / CVE List V5
Vulnerability Description
Flux notification-controller is the event forwarder and notification dispatcher for the GitOps Toolkit controllers. Prior to 1.8.3, the gcr Receiver type in Flux notification-controller does not validate the email claim of Google OIDC tokens used for Pub/Sub push authentication. This allows any valid Google-issued token, to authenticate against the Receiver webhook endpoint, triggering unauthorized Flux reconciliations. Exploitation requires the attacker to know the Receiver's webhook URL. The webhook path is generated as /hook/sha256sum(token+name+namespace), where the token is a random string stored in a Kubernetes Secret. There is no API or endpoint that enumerates webhook URLs. An attacker cannot discover the path without either having access to the cluster and permissions to read the Receiver's .status.webhookPath in the target namespace, or obtaining the URL through other means (e.g. leaked secrets or access to Pub/Sub config). Upon successful authentication, the controller triggers a reconciliation for all resources listed in the Receiver's .spec.resources. However, the practical impact is limited: Flux reconciliation is idempotent, so if the desired state in the configured sources (Git, OCI, Helm) has not changed, the reconciliation results in a no-op with no effect on cluster state. Additionally, Flux controllers deduplicate reconciliation requests, sending many requests in a short period results in only a single reconciliation being processed. This vulnerability is fixed in 1.8.3.
来源: CVE Program / CVE List V5
CVSS Information
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:L/A:N
来源: CVE Program / CVE List V5
Vulnerability Type
认证机制不恰当
来源: CVE Program / CVE List V5
Vulnerability Title
notification-controller 数据伪造问题漏洞
来源: 中国国家信息安全漏洞库 CNNVD
Vulnerability Description
notification-controller是Flux project开源的一个GitOps通知控制器。 notification-controller 1.8.3之前版本存在数据伪造问题漏洞，该漏洞源于未验证Google OIDC令牌的email声明，可能导致任何有效的Google签发令牌都能触发未经授权的Flux协调。
来源: 中国国家信息安全漏洞库 CNNVD
CVSS Information
N/A
来源: 中国国家信息安全漏洞库 CNNVD
Vulnerability Type
N/A
来源: 中国国家信息安全漏洞库 CNNVD
受影响产品
| 厂商 | 产品 | 影响版本 | CPE | 订阅 |
|---|---|---|---|---|
| fluxcd | notification-controller | < 1.8.3 | - |
|
二、漏洞 CVE-2026-40109 的公开POC
| # | POC 描述 | 源链接 | 神龙链接 |
|---|
AI 生成 POC
高级
未找到公开 POC。
登录以生成 AI POC三、漏洞 CVE-2026-40109 的情报信息
请登录查看更多情报信息。
CVE-2026-40109 补丁与修复 (1)
CVE-2026-40109 厂商安全公告 (1)
IV. Related Vulnerabilities
V. Comments for CVE-2026-40109
暂无评论