CVE 8.6 HIGH

Gradle’s failure to disable repositories failing to answer can expose builds to malicious artifacts_CVE-2026-22865

8.6 / 10
HIGH
CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:P/VC:H/VI:H/VA:N/SC:N/SI:H/SA:N

Description

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.

AI Analysis

Gradle's failure to disable repositories that fail to answer can expose builds to malicious artifacts

Basic Information

ID CVE-2026-22865
Source GitHub_M
Published Jan 16, 2026 at 22:46

Affected Product

Vendor gradle
Product gradle
Version < 9.3.0
Affected Versions gradle gradle < 9.3.0

CWE Classification

AI Assessment

AI Score 8.6 / 10
AI Severity High
Vendor Gradle Inc.
Product Gradle
Version < 9.3.0

References

💭 Join the Security Discussion

🔒 Your email address will not be published. Required fields are marked *

⚠️ Please be respectful and constructive in your comments. Security discussions should remain professional.