CVE-2026-22816: Gradle fails to disable repositories which can expose builds to malicious artifacts

Vulnerability summary

CVE-2026-22816 is a high (CVSS 8.6) Download of Code Without Integrity Check vulnerability in gradle. EPSS estimates a 0.17% chance of exploitation in the next 30 days, higher than 6.8% of scored vulnerabilities.

Timeline

1. 16-01-2026
   PublishedVulnerability first disclosed.
2. 20-01-2026
   Last modifiedVulnerability information updated.

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. If a Gradle build used an unresolvable host name, Gradle would continue to work as long as all dependencies could be resolved from another repository. An unresolvable host name could be caused by allowing a repository's domain name registration to lapse or typo-ing the real domain name. This behavior could allow an attacker to register a service under the host name used by the build and serve malicious artifacts. The attack requires the repository to be listed before others in the build configuration. Gradle has introduced a change in behavior in Gradle 9.3.0 to stop searching other repositories when encountering these errors.

• CWE-494Download of Code Without Integrity CheckThe product downloads source code or an executable from a remote location and executes the code without sufficiently verifying the origin and integrity of the code.
• CWE-829Inclusion of Functionality from Untrusted Control SphereThe product imports, requires, or includes executable functionality (such as a library) from a source that is outside of the intended control sphere.