← Back to CVE List
Vulnerability Intelligence Report
Gradle's failure to disable repositories failing to answer can expose builds to malicious artifacts

CVE-2026-22865

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.

No Active Exploit Signals
CVSS Base Score
8.6
HIGH
EPSS Probability:0.14%
Executive Threat Verdict
Evaluating...
Evaluating Threat Landscape...
Assessing known weaponization, exploitation telemetry, and federal advisories.
Attack Surface
—
Authentication
—
Weaponization
—
SSVC Action
—

Weaknesses (CWE)

CWE-494 ↗CWE-494: Download of Code Without Integrity Check
CWE-829 ↗CWE-829: Inclusion of Functionality from Untrusted Control Sphere

Affected Products & Versions

Vendor Product Affected Versions
gradle gradle < 9.3.0 (affected)

References & Technical Advisories

No reference links found.

Threat Intelligence Signals

EPSS Score
0.135%

Identity & Timeline

StatusPUBLISHED
Assigning AuthorityGitHub, Inc. · Vendor · USA
Reserved2026-01-12T16:20:16
Published2026-01-16T22:46:19
Last Updated2026-01-20T14:47:41

LINK COPIED TO CLIPBOARD