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

Enalean

tuleap

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 identity is present in BlackTree CVE records, but no product-specific publisher support or retirement history is currently registered in Lifecycle.

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-2022-31058 29 Jun 2022 < 13.9.99.95 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-31063 29 Jun 2022 < 13.9.99.111 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-31032 29 Jun 2022 < 13.9.99.58 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-24896 6 Jun 2022 < 13.7.99.239 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-43806 15 Dec 2021 < 13.2.99.155; >= 13.1-1, < 13.1-7; >= 13.2-1, < 13.2-6 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-41276 15 Dec 2021 < 13.2.99.31; >= 13.1-1, < 13.1-5; >= 13.2-1, < 13.2-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-43782 15 Dec 2021 < 13.2.99.83; >= 13.1-1, < 13.1-6; >= 13.2-1, < 13.2-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-41154 18 Oct 2021 < 11.17.99.144; >= 11.17-1, < 11.17-5; >= 11.16-1, < 11.16-7 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-41155 18 Oct 2021 < 11.17.99.146; >= 11.17-1, < 11.17-5; >= 11.16-1, < 11.16-7 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-41148 15 Oct 2021 < 11.16.99.173; >= 11.16-1, < 11.16-6; >= 11.15-1, < 11.15-8 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-41147 15 Oct 2021 < 11.16.99.173; >= 11.16-1, < 11.16-6; >= 11.15-1, < 11.15-8 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-41142 14 Oct 2021 < 12.11.99.25; >= 12.11-1, < 12.11-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 ↗

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.