CVE-2026-22816 Details
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.
A vulnerability exists in Gradle's dependency resolution process in versions prior to 9.3.0 and 8.14.4. When a build encounters certain connection errors, Gradle may not disable the problematic repository, allowing the build to continue and potentially resolve dependencies from other repositories. This behavior could be exploited by an attacker to serve malicious artifacts, especially if the repository with the unresolvable host name is listed before others in the build configuration. Gradle 9.3.0 and 8.14.4 have addressed this issue by changing the repository resolution behavior to prioritize security and build reproducibility.
Upgrade to Gradle version 9.3.0 or 8.14.4. If an immediate upgrade is not possible, review and update repository declarations to remove unused or outdated entries. Consider using Gradle's dependency verification feature to ensure that only expected dependencies are resolved.
Metrics
CVSS 4.0 Severity and Vector Strings:
CVSS 3.x Severity and Vector Strings:
No data available for CVSS Version 2.0 on this CVE.
CISA-ADP
Assessed Jan 20, 2026References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.
Weakness Enumeration
| CWE-ID | CWE Name | Source |
|---|---|---|
| CWE-494 | Download of Code Without Integrity Check | [email protected] |
| CWE-829 | Inclusion of Functionality from Untrusted Control Sphere | [email protected] |
Affected Products
| Product | Versions |
|---|---|
| gradle gradle | < 8.14.4 >= 9.0.0, < 9.3.0 |
CPE
Remediation
| |
Change History
4 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Jun 17, 2026 | CVE Modified | [email protected] |
| Jun 17, 2026 | CVE Modified | CISA-ADP |
| Feb 18, 2026 | Initial Analysis | [email protected] |
| Jan 16, 2026 | New CVE Received | [email protected] |