p PatchFirst

PatchFirst · Latest vulnerabilities

gradle vulnerabilities

Vulnerabilities published for gradle in the last 30 days: 0. Listed in the KEV catalogue: 0.

Filter vulnerabilities
Clear filters

Vulnerabilities: 5

  1. CVE-2026-22865

    High · CVSS 8.6EPSS 0.16%Fix available

    Gradle's failure to disable repositories failing to answer can expose builds to malicious artifacts

    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. An exception like NoHttpResponseException can indicate transient errors. If the errors persist after a maximum number of retries, Gradle would continue to the next repository. This behavior could allow an attacker to disrup

    • Update to 8.14.4-r0
    Published Updated
  2. CVE-2026-22816

    High · CVSS 8.6EPSS 0.17%Fix available

    Gradle fails to disable repositories which can expose builds to malicious artifacts

    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 dom

    • Update to 8.14.4-r0
    Published Updated
  3. CVE-2023-26053

    Medium · CVSS 6.6EPSS 0.99%Fix available

    Gradle usage of long IDs for PGP keys opens potential for collision attacks

    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 `trusted-key` or `pgp` element in their dependency verification metadata file. The fix is to fail dependency verification if anything but a fingerprint is used in a trust element in dependency verification metadata. The problem is fixed in Gradle 8.0 and above. The problem is also patched in Gradle 6.9.4 and 7.6.1. As a workaround, use only full fingerprint IDs for `trusted-key` or `pgp`

    • Update to 7.6.1-r0
    Published Updated
  4. CVE-2021-32751

    High · CVSS 7.5EPSS 2.71%Fix available

    Arbitrary code execution via specially crafted environment variables

    Gradle is a build tool with a focus on build automation. In versions prior to 7.2, start scripts generated by the `application` plugin and the `gradlew` script are both vulnerable to arbitrary code execution when an attacker is able to change environment variables for the user running the script. This may impact those who use `gradlew` on Unix-like systems or use the scripts generated by Gradle in thieir application on Unix-like systems. For this vulnerability to be exploitable, an attacker needs to be able to set the value of particular environment variables and have those environment variables be seen by the vulnerable scripts. This issue h

    • Update to 7.2-r0
    Published Updated
  5. CVE-2020-11979

    High · CVSS 7.5EPSS 7.76%Fix available

    CVE-2020-11979

    As mitigation for CVE-2020-1945 Apache Ant 1.10.8 changed the permissions of temporary files it created so that only the current user was allowed to access them. Unfortunately the fixcrlf task deleted the temporary file and created a new one without said protection, effectively nullifying the effort. This would still allow an attacker to inject modified source files into the build process.

    • Update to 6.8.3-r0
    Published Updated

Check your server

Check your installed stack and versions against the current vulnerability feeds.

Check your server →