Gradle's failure to disable repositories failing to answer can expose builds to malicious artifacts
概要
Gradle's failure to disable repositories failing to answer can expose builds to malicious artifacts
原文の説明
取得元が公開している説明をそのまま載せています (多くは英語)。
Gradle is a build automation tool, and its native-platform tool provides Java bindings for native APIs. When resolving dependencies in versions before 9.3.0, some exceptions were not treated as fatal errors and would not cause a repository to be disabled. If a build encountered one of these exceptions, Gradle would continue to the next repository in the list and potentially resolve dependencies from a different repository. An exception like NoHttpResponseException can indicate transient errors. If the errors persist after a maximum number of retries, Gradle would continue to the next repository. This behavior could allow an attacker to disrupt the service of a repository and leverage another repository to serve malicious artifacts. This attack requires the attacker to have control over a repository after the disrupted repository. Gradle has introduced a change in behavior in Gradle 9.3.0 to stop searching other repositories when encountering these errors.
出典: OSV.dev (Open Source Vulnerabilities) NVD GitHub Advisory OSV
影響パッケージ
ディストリビューション別の修正状況
各ディストリビューションが公開している、この CVE の修正パッケージ
- Debian DEBIAN-CVE-2026-22865 gradle
- Ubuntu UBUNTU-CVE-2026-22865 gradle
参照URL
- advisory github.com
- advisory nvd.nist.gov
- advisory github.com