【高危】fleet：拒绝服务风险（GHSA-jmf4-m7j9-g72r）

安全情报快照 · 风险级别：高危 · CVSS：7.5 · CVE-2026-44937 · GHSA-jmf4-m7j9-g72r

先看结论

fleet存在拒绝服务风险，>= 0.15.0, < 0.15.2 受影响，建议升级至 0.15.2。

影响范围

生态	组件	受影响版本	首个修复版本
go	`github.com/rancher/fleet`	>= 0.15.0, < 0.15.2	0.15.2
go	`github.com/rancher/fleet`	>= 0.14.0, < 0.14.6	0.14.6
go	`github.com/rancher/fleet`	>= 0.13.0, < 0.13.11	0.13.11
go	`github.com/rancher/fleet`	>= 0.12.0, < 0.12.15	0.12.15

处置建议

优先将 github.com/rancher/fleet 升级至 0.15.2 或更高版本；升级前请结合业务依赖完成兼容性验证。

上游技术详情（原文）

Impact

A vulnerability has been identified in Fleet when the webhook endpoint is configured without a secret; an attacker can forge webhook requests. The attacker doesn't need to know the specific repository or path configured in the GitRepo resource to make Fleet process these requests.

An attacker can exploit this vulnerability to cause the following impacts:

Trigger continuous repository re-cloning, which increases network traffic and can deplete resources on the management cluster.
Downgrade running services to any historical revision available in the remote Git repository. This risk applies if the attacker has read access to the target Git repository and knows its configured path.

Please consult the associated MITRE ATT&CK - Technique - T1499.004: Endpoint Denial of Service for further information about this category of attack.

Patches

To resolve this vulnerability, upgrade Fleet to a patched version. This upgrade version escapes the URL and path to the remote repository received from webhooks, which prevents regular expressions from being used as a replacement for the URL and path.

Patched versions of Fleet include releases v0.15.2, v0.14.6, 0.13.11, and v0.12.15.

Workarounds

If you can't upgrade to a fixed version, please make sure to only enable webhooks with a shared secret.

Credits

This security issue was reported by the following collaborators according to our responsible disclosure policy:

Radisauskas Arnoldas from NATO and the NATO Cyber Security Centre (NCSC).

References

If you have any questions or comments about this advisory:

Reach out to the SUSE Rancher Security team for security related inquiries.
Open an issue in the Rancher repository.
Verify with our support matrix and product support lifecycle.

来源与许可

本页自动同步 GitHub Advisory Database 的公开数据，并保留上游原文供核验；不宣称原创分析。数据许可：CC-BY-4.0。