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

GitLab

GitLab Runner

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 GitLab Runner. 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-2022-2251 17 Jan 2023 <15.3.5; >=15.4, <15.4.4; >=15.5, <15.5.2 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2021-39947 6 Jun 2022 <14.3.4; >=14.4, <14.4.2; >=14.5, <14.5.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-2021-39939 13 Dec 2021 >=13.7, <14.3.6; >=14.4, <14.4.4; >=14.5, <14.5.2 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2020-13327 22 Oct 2020 >=13.4.0, <13.4.2; >=13.3.0, <13.3.7; >=13.2.0, <13.2.10 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2020-13347 7 Oct 2020 >=12.0.0, <13.2.4; >=13.3.0, <13.3.2; >=13.4.0, <13.4.1 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2020-13295 10 Aug 2020 >=1.0, <13.0.12; >=13.1, <13.1.6; >=13.2, <13.2.3 No fixed version is explicitly recorded in the structured CVE data. Use CVE record

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.