CVE-2026-22816 Gradle fails to disable repositories which can expose builds to malicious artifacts
Attackers can serve malicious artifacts by registering lapsed or typoed repository domains, leading to code execution during builds.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- A user has to click or open something
- Fix
- Available
What is CVE-2026-22816?
CVE-2026-22816 is a high-severity vulnerability in gradle, published on 16 Jan 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Official 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.
Which versions are affected by CVE-2026-22816?
1 open source package ship an affected version, including gradle. It affects 1 product.
| Package | Affected | Fixed in |
|---|---|---|
gradle Bitnami | All versions | 9.3.0 |
Products include Gradle Gradle.
How do I fix CVE-2026-22816?
Upgrade gradle to 9.3.0 or later.
Is CVE-2026-22816 being exploited?
There is no known exploitation of CVE-2026-22816 in the wild and no public exploit code.
Other vulnerabilities in gradle
- CVE-2019-15052 Information disclosure in n/a
- CVE-2016-6199 Deserialization in n/a
- CVE-2021-29428 Local privilege escalation through system temporary directory
- CVE-2026-22865 Gradle's failure to disable repositories failing to answer can expose builds to malicious artifacts
- CVE-2021-41588 Deserialization in n/a
Sources
Also known as BELL-CVE-2026-22816, BIT-gradle-2026-22816, DEBIAN-CVE-2026-22816, GHSA-w78c-w6vf-rw82, MINI-3qqw-cf22-vggw, MINI-pj2c-832m-86f4 and 2 more.