How severe is CVE-2023-26053?

CVE-2023-26053 has a CVSS 3.x base score of 6.6, rated medium severity. It is exploitable over network with high attack complexity, requires high privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability high.

Is CVE-2023-26053 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (59th percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2023-26053?

CVE-2023-26053 affects Gradle. See the affected-products list for the exact vulnerable versions.

How do I fix CVE-2023-26053?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.

When was CVE-2023-26053 published?

CVE-2023-26053 was published on 2023-03-02 and last updated on 2026-06-17.

CVE-2023-26053

CVE-2023-26053 is a medium-severity vulnerability in Gradle with a CVSS 3.x base score of 6.6. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-829.

Key facts

Severity: Medium (CVSS 3.x base score 6.6)
EPSS exploit prediction: 1% (59th percentile)
Actively exploited: Not listed in CISA KEV
Weakness: CWE-829
Affected product: Gradle
Published: 2023-03-02
Last modified: 2026-06-17

Description

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` element in the metadata is a protection against this issue.

Frequently asked questions

What is CVE-2023-26053?: 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` element in the metadata is a protection against this issue.
How severe is CVE-2023-26053?: CVE-2023-26053 has a CVSS 3.x base score of 6.6, rated medium severity. It is exploitable over network with high attack complexity, requires high privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability high.
Is CVE-2023-26053 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (59th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2023-26053?: CVE-2023-26053 affects Gradle. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2023-26053?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
When was CVE-2023-26053 published?: CVE-2023-26053 was published on 2023-03-02 and last updated on 2026-06-17.

References

Affected products (1)

cpe:2.3:a:gradle:gradle:*:*:*:*:*:*:*:*

More vulnerabilities in Gradle

CVE-2019-15052 — Critical (CVSS 9.8): The HTTP client in Gradle before 5.6 sends authentication credentials originally destined for the configured host. If…
CVE-2016-6199 — Critical (CVSS 9.8): ObjectSocketWrapper.java in Gradle 2.12 allows remote attackers to execute arbitrary code via a crafted serialized…
CVE-2021-29428 — High (CVSS 8.8): In Gradle before version 7.0, on Unix-like systems, the system temporary directory can be created with open permissions…
CVE-2021-41588 — High (CVSS 8.1): In Gradle Enterprise before 2021.1.3, a crafted request can trigger deserialization of arbitrary unsafe Java objects.…
CVE-2021-29427 — High (CVSS 8.0): In Gradle from version 5.1 and before version 7.0 there is a vulnerability which can lead to information disclosure…
CVE-2022-23630 — High (CVSS 7.5): Gradle is a build tool with a focus on build automation and support for multi-language development. In some cases,…

All CVEs affecting Gradle →

Other CWE-829 vulnerabilities

CVE-2026-1699 — Critical (CVSS 10.0): In the Eclipse Theia Website repository, the GitHub Actions workflow .github/workflows/preview.yml used…
CVE-2025-70974 — Critical (CVSS 10.0): Fastjson before 1.2.48 mishandles autoType because, when an @type key is in a JSON document, and the value of that key…
CVE-2025-0982 — Critical (CVSS 10.0): Sandbox escape in the JavaScript Task feature of Google Cloud Application Integration allows an actor to execute…
CVE-2021-41037 — Critical (CVSS 10.0): In Eclipse p2, installable units are able to alter the Eclipse Platform installation and the local machine via…
CVE-2022-1161 — Critical (CVSS 10.0): An attacker with the ability to modify a user program may change user program code on some ControlLogix, CompactLogix,…
CVE-2020-4561 — Critical (CVSS 10.0): IBM Cognos Analytics 11.0 and 11.1 DQM API allows submitting of all control requests in unauthenticated sessions. This…

Browse all CWE-829 vulnerabilities →