CVE-2026-22816
CVE-2026-22816 · Gradle fails to disable repositories which can expose builds to malicious artifacts
CVSS 8.6 · High · EPSS 0.2% · Fix available
Compare with your installed version
Affected products and known fixed versions are public information. Compare them with your installed version.
- gradleNo fix published
- gradle Alpine 3.23Update to 8.14.4-r0
- gradle Alpine 3.24Update to 8.14.4-r0
- gradle Debian 12No fix published
- and 10 more
Check the installed version:
apk list -I -o gradledpkg-query -W -f='${source:Package} ${binary:Package} ${Version}\n' | awk '$1=="gradle"'Assess your server’s risks
The free check gives you a rating and a risk summary by technology stack, without signing up. It does not answer whether this particular vulnerability affects you.
Monitoring matches public information against your servers’ software. Detailed findings for your servers include the order of updates.
curl -fsSL https://patchfirst.dev/check.sh | shChannels carry general technology news; monitoring reports new findings on your servers in your dashboard, through browser notifications, in Telegram or via a webhook.
This page contains facts from public vulnerability sources. Check the original advisory before updating.
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.
- Published
- Updated
Stack: system
Affected products and versions
gradle
- Versions
- < 9.3.0: Affected
No fix published
gradle Alpine 3.23
- Affected ranges
- ECOSYSTEM: < 8.14.4-r0
Update to 8.14.4-r0
gradle Alpine 3.24
- Affected ranges
- ECOSYSTEM: < 8.14.4-r0
Update to 8.14.4-r0
gradle Debian 12
- Versions
- 4.4.1-18
- 4.4.1-19
- 4.4.1-20
- 4.4.1-21
- 4.4.1-22
- 4.4.1-23
All versions (9)
- 4.5.1-1
- 4.6-1
- 4.6-2
- Affected ranges
- ECOSYSTEM: (−∞, +∞)
No fix published
gradle Debian 13
- Versions
- 4.4.1-22
- 4.4.1-23
- 4.5.1-1
- 4.6-1
- 4.6-2
- Affected ranges
- ECOSYSTEM: (−∞, +∞)
No fix published
gradle Debian 14
- Versions
- 4.4.1-22
- 4.4.1-23
- 4.5.1-1
- 4.6-1
- 4.6-2
- Affected ranges
- ECOSYSTEM: (−∞, +∞)
No fix published
gradle Ubuntu 16.04 LTS
- Versions
- 2.5-3
- 2.7-1
- 2.7-2
- 2.7-3
- 2.10-1
- Affected ranges
- ECOSYSTEM: (−∞, +∞)
No fix published
gradle Ubuntu Pro 18.04 LTS
- Versions
- 3.2.1-3build2
- 3.2.1-4
- 3.2.1-5
- 3.4.1-4
- 3.4.1-6
- 3.4.1-7ubuntu1
All versions (8)
- 4.4.1-5ubuntu2~18.04
- 4.4.1-5ubuntu2~18.04+esm1
- Affected ranges
- ECOSYSTEM: (−∞, +∞)
No fix published
gradle Ubuntu 20.04 LTS
- Versions
- 4.4.1-8
- 4.4.1-9
- 4.4.1-10
- Affected ranges
- ECOSYSTEM: (−∞, +∞)
No fix published
gradle Ubuntu 22.04 LTS
- Versions
- 4.4.1-13
- Affected ranges
- ECOSYSTEM: (−∞, +∞)
No fix published
gradle Ubuntu 24.04 LTS
- Versions
- 4.4.1-18
- 4.4.1-20
- Affected ranges
- ECOSYSTEM: (−∞, +∞)
No fix published
gradle Ubuntu 25.10
- Versions
- 4.4.1-22
- Affected ranges
- ECOSYSTEM: (−∞, +∞)
No fix published
gradle Ubuntu 26.10
- Versions
- 4.4.1-22ubuntu1
- 4.4.1-23
- Affected ranges
- ECOSYSTEM: (−∞, +∞)
No fix published
gradle Ubuntu 26.04 LTS
- Versions
- 4.4.1-22
- 4.4.1-22build1
- 4.4.1-22ubuntu1
- Affected ranges
- ECOSYSTEM: (−∞, +∞)
No fix published