Gradle vulnerabilities
We track 14 vulnerabilities in Gradle products across 3 products. 14 are rated high or critical, and none are known to be exploited. The most recent was published on January 29, 2026.
Latest Gradle vulnerabilities
- 7.8 High severity
gradle-completion: Improper Neutralization of Special Elements used in an OS Command
gradle-completion provides Bash and Zsh completion support for Gradle. A command injection vulnerability was found in gradle-completion up to and including 9.3.0 that allows arbitrary code execution when a user triggers Bash tab completion in a project contain
- 7.4 High severity
gradle: Download of Code Without Integrity Check
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
- 7.4 High severity
gradle: Download of Code Without Integrity Check
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
- 8.8 High severity
gradle: Creation of Temporary File With Insecure Permissions
Gradle is a build automation tool, and its native-platform tool provides Java bindings for native APIs. On Unix-like systems, the system temporary directory can be created with open permissions that allow multiple users to create and delete files within it. Th
- 7.1 High severity
Enterprise: Incorrect Permission Assignment for Critical Resource
Develocity (formerly Gradle Enterprise) before 2024.1.8 has Incorrect Access Control. Project-level access control configuration was introduced in Enterprise Config schema version 8. Migration functionality from schema version 8 to versions 9 and 10 (in affect
- 8.3 High severity
Enterprise: Insertion of Sensitive Information Into Sent Data
Develocity (formerly Gradle Enterprise) before 2024.3.1 allows an attacker who has network access to a Develocity server to obtain the hashed password of the system user. The hash algorithm used by Develocity was chosen according to best practices for password
- 9.8 Critical severity
Enterprise: Weak Password Requirements
In Gradle Enterprise before 2023.1, a remote attacker may be able to gain access to a new installation (in certain installation scenarios) because of a non-unique initial system user password. Although this password must be changed upon the first login, it is
- 8.1 High severity
gradle: Improper Limitation of a Pathname to a Restricted Directory
Gradle is a build tool with a focus on build automation and support for multi-language development. In affected versions when unpacking Tar archives, Gradle did not check that files could be written outside of the unpack location. This could lead to important
- 9.8 Critical severity
gradle: Inclusion of Functionality from Untrusted Control Sphere
Gradle is a build tool with a focus on build automation and support for multi-language development. This is a collision attack on long IDs (64bits) for PGP keys. Users of dependency verification in Gradle are vulnerable if they use long IDs for PGP keys in a `
- 7.5 High severity
Enterprise: Insufficiently Protected Credentials
A credential-exposure vulnerability in the support-bundle mechanism in Gradle Enterprise 2022.3 through 2022.3.3 allows remote attackers to access a subset of application data (e.g., cleartext credentials). This is fixed in 2022.3.3.
- 7.5 High severity
Enterprise: Incorrect Authorization
An access-control vulnerability in Gradle Enterprise 2022.4 through 2022.3.1 allows remote attackers to prevent backups from occurring, and send emails with arbitrary text content to the configured installation-administrator contact address, via HTTP access to
- 9.8 Critical severity
Enterprise: Incorrect Default Permissions
Gradle Enterprise before 2022.1 allows remote code execution if the installation process did not specify an initial configuration file. The configuration allows certain anonymous access to administration and an API.
- 8.1 High severity
Enterprise: Incorrect Default Permissions
In Gradle Enterprise before 2021.4.2, the default built-in build cache configuration allowed anonymous write access. If this was not manually changed, a malicious actor with network access to the build cache could potentially populate it with manipulated entri
- 7.5 High severity
gradle: Inclusion of Functionality from Untrusted Control Sphere
Gradle is a build tool with a focus on build automation and support for multi-language development. In some cases, Gradle may skip that verification and accept a dependency that would otherwise fail the build as an untrusted external artifact. This occurs when