CVE-2026-22865

High

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.

SeverityHigh
CVSS7.4
Exploit probability—
ProductGradle
PublishedJan 16, 2026
First seenJan 16, 2026

How to fix

Update
  • gradle gradle8.14.4, 9.3.0 or later

Affected products

ProductAffected versionsFixed in
gradle gradlev < 8.14.4, 9.0.0 ≤ v < 9.3.08.14.4, 9.3.0

Check your version

Choose the product and enter the version you run to see whether it falls in the affected range.

In the Intelligence 360 plan

Attack Surface Management

See the assets tied to your domains, the technologies they run and known vulnerabilities in one list.

CVE-2026-22865 · Gradle · Dark Radar