Evidence-linked product lifecycle intelligenceSUPPORT · SECURITY · RETIREMENT
← Search results
CVE-LINKED INVENTORY14 SECURITY RECORDS

gradle

gradle

Affected and fixed version statements observed in the public BlackTree CVE catalogue. These statements describe vulnerability scope, not publisher support entitlement.

Lifecycle evidence status

This CVE identity is linked to the Lifecycle record Gradle. Use that record for publisher support phases and retirement dates.

A missing support date does not mean the product is supported. CVE publication dates and affected-version ranges must not be interpreted as EOL dates.

CVE-observed version history

CVEPublishedAffected versionsFixed version informationPublisher evidence
CVE-2026-22865 16 Jan 2026 < 9.3.0 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-22816 16 Jan 2026 < 9.3.0 An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. Update reference ↗
CVE-2025-27148 25 Feb 2025 = 8.12 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2023-42445 6 Oct 2023 < 8.4; < 7.6.3 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2023-44387 5 Oct 2023 >= 7.6.0, < 7.6.3; < 8.4.0 An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. Update reference ↗
CVE-2023-35946 30 Jun 2023 < 7.6.2; >= 8.0, < 8.2 An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. Update reference ↗
CVE-2023-35947 30 Jun 2023 < 7.6.1; >= 8.0, < 8.2 An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. Update reference ↗
CVE-2023-26053 2 Mar 2023 >= 6.2, < 6.9.4; >= 7.0.0, < 7.6.1 An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. Update reference ↗
CVE-2022-31156 14 Jul 2022 >= 6.2, <= 7.4.2 An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. Update reference ↗
CVE-2022-23630 10 Feb 2022 >= 6.2, < 7.4 An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. Update reference ↗
CVE-2021-32751 20 Jul 2021 < 7.2 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2021-29427 13 Apr 2021 >= 5.1, <= 6.8.3 An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. Update reference ↗
CVE-2021-29428 13 Apr 2021 < 7.0 An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. Update reference ↗
CVE-2021-29429 12 Apr 2021 < 7.0 An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. Update reference ↗

How this record is maintained

The CVE inventory is reconciled automatically from cve.blacktree.nl. Exact identity matches link to existing Lifecycle product or package histories. Unmatched products stay in a prioritised publisher-source research queue, and Lifecycle marks the date gap instead of inferring a support boundary from vulnerability data.