{"answers":{"affected":"1 open source package ship an affected version, including gradle. It affects 1 product.","exploited":"There is no known exploitation of CVE-2023-26053 in the wild and no public exploit code.","fix":"Upgrade gradle to a fixed version for your release line: 6.9.4 or 7.6.1.","what":"CVE-2023-26053 is a medium-severity vulnerability in gradle, published on 2 Mar 2023. An attacker needs administrator access to exploit it, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2023-26053 and fix it if it is affected.\n\nWhat it is: CVE-2023-26053 is a medium-severity vulnerability in gradle, published on 2 Mar 2023. An attacker needs administrator access to exploit it, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2023-26053 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- gradle (Bitnami): affected from 6.2.0; fixed in 6.9.4, 7.6.1\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2023-26053/ (Markdown: https://insights.sbomify.com/CVE-2023-26053/index.md)","id":"CVE-2023-26053","markdown":"https://insights.sbomify.com/CVE-2023-26053/index.md","name":"CVE-2023-26053","record":{"aliases":["BIT-gradle-2023-26053","CLEANSTART-2026-RH82796","CLEANSTART-2026-UI97459","GHSA-c724-3xg7-g3hf","UBUNTU-CVE-2023-26053"],"analysis":{"component_type":"developer_tool","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":true,"product_category":"Gradle build tool","requires_auth":"high_privilege","summary":"Attackers can bypass dependency verification in Gradle by exploiting PGP key ID collisions, allowing malicious dependencies to be trusted.","user_interaction":"not_required","vuln_class":"other"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"gradle","vendor":"gradle"}],"cvss":{"score":6.6,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-829","name":"Inclusion of Functionality from Untrusted Control Sphere"}],"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.","ecosystems":["Bitnami"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Gradle usage of long IDs for PGP keys opens potential for collision attacks","id":"CVE-2023-26053","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Bitnami","product":null,"products":[],"type":"other","year":"2023"},"n_packages":1,"n_references":3,"next":{"headline":"Credentials inlined to Git URLs could end up in provenance attestation in BuildKit","id":"CVE-2023-26054"},"packages":[{"ecosystem":"Bitnami","fixed":["6.9.4","7.6.1"],"introduced":["6.2.0","7.0.0"],"last_affected":[],"package":"gradle","purl":"pkg:bitnami/gradle","source":"BIT-gradle-2023-26053"}],"prev":{"headline":"Saleor is vulnerable to unauthenticated information disclosure via Python exceptions","id":"CVE-2023-26052"},"products":["gradle"],"published":"2023-03-02","related":[{"cvss_score":9.8,"headline":"Information disclosure in n/a","id":"CVE-2019-15052","kev_date_added":null,"published":"2019-08-14"},{"cvss_score":9.8,"headline":"Deserialization in n/a","id":"CVE-2016-6199","kev_date_added":null,"published":"2017-02-07"},{"cvss_score":8.8,"headline":"Local privilege escalation through system temporary directory","id":"CVE-2021-29428","kev_date_added":null,"published":"2021-04-13"},{"cvss_score":8.6,"headline":"Gradle fails to disable repositories which can expose builds to malicious artifacts","id":"CVE-2026-22816","kev_date_added":null,"published":"2026-01-16"},{"cvss_score":8.6,"headline":"Gradle's failure to disable repositories failing to answer can expose builds to malicious artifacts","id":"CVE-2026-22865","kev_date_added":null,"published":"2026-01-16"},{"cvss_score":8.1,"headline":"Deserialization in n/a","id":"CVE-2021-41588","kev_date_added":null,"published":"2021-09-24"},{"cvss_score":8,"headline":"Repository content filters do not work in Settings pluginManagement","id":"CVE-2021-29427","kev_date_added":null,"published":"2021-04-13"}],"sources":[{"class":"attribution","licence":"Apache-2.0","name":"Bitnami","prefix":"BIT"},{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2025-03-05","vendors":["gradle"]},"summary":"Attackers can bypass dependency verification in Gradle by exploiting PGP key ID collisions, allowing malicious dependencies to be trusted.","url":"https://insights.sbomify.com/CVE-2023-26053/"}