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

GitLab

GitLab

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. 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-2023-0989 29 Sep 2023 < 16.2.8; 16.3 < 16.3.5; 16.4 < 16.4.1 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2023-2233 29 Sep 2023 11.8 < 16.2.8; 16.3 < 16.3.5; 16.4 < 16.4.1 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2023-3115 29 Sep 2023 11.11 < 16.2.8; 16.3 < 16.3.5; 16.4 < 16.4.1 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2023-3920 29 Sep 2023 11.2 < 16.2.8; 16.3 < 16.3.5; 16.4 < 16.4.1 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2023-3917 29 Sep 2023 < 16.2.8; 16.3 < 16.3.5; 16.4 < 16.4.1 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2023-3914 29 Sep 2023 < 16.2.8; 16.3 < 16.3.5; 16.4 < 16.4.1 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2023-3906 29 Sep 2023 12.3 < 16.2.8; 16.3 < 16.3.5; 16.4 < 16.4.1 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2023-3979 29 Sep 2023 10.6 < 16.2.8; 16.3 < 16.3.5; 16.4 < 16.4.1 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2023-4532 29 Sep 2023 16.2 < 16.2.8; 16.3 < 16.3.5; 16.4 < 16.4.1 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2023-5009 19 Sep 2023 13.12 < 16.2.7; 16.3 < 16.3.4 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2023-4630 11 Sep 2023 10.6 < 16.1.5; 16.2 < 16.2.5; 16.3 < 16.3.1 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2023-3210 1 Sep 2023 15.11 < 16.1.5; 16.2 < 16.2.5; 16.3 < 16.3.1 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2023-3950 1 Sep 2023 16.2 < 16.2.5; 16.3 < 16.3.1 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2023-4018 1 Sep 2023 16.2 < 16.2.5; 16.3 < 16.3.1 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2023-4378 1 Sep 2023 11.8 < 16.1.5; 16.2 < 16.2.5; 16.3 < 16.3.1 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2023-4647 1 Sep 2023 15.2 < 16.1.5; 16.2 < 16.2.5; 16.3 < 16.3.1 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2022-4343 1 Sep 2023 13.12 < 16.1.5; 16.2 < 16.2.5; 16.3 < 16.3.1 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2023-0120 1 Sep 2023 10.0 < 16.1.5; 16.2 < 16.2.5; 16.3 < 16.3.1 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2023-1279 1 Sep 2023 4.1 < 16.1.5; 16.2 < 16.2.5; 16.3 < 16.3.1 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2023-1555 1 Sep 2023 15.2 < 16.1.5; 16.2 < 16.2.5; 16.3 < 16.3.1 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2023-3205 1 Sep 2023 15.11 < 16.1.5; 16.2 < 16.2.5; 16.3 < 16.3.1 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2023-3915 1 Sep 2023 16.1 < 16.1.5; 16.2 < 16.2.5; 16.3 < 16.3.1 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2023-4522 30 Aug 2023 < 16.2.0 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2023-4002 4 Aug 2023 14.1 < 16.0.8; 16.1.0 < 16.1.3; 16.2.0 < 16.2.2 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2023-4008 3 Aug 2023 15.9 < 16.0.8; 16.1 < 16.1.3; 16.2 < 16.2.2 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2023-3932 3 Aug 2023 13.12 < 16.0.8; 16.1.0 < 16.1.3; 16.2.0 < 16.2.2 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2023-2022 2 Aug 2023 < 16.0.8; 16.1.0 < 16.1.3; 16.2.0 < 16.2.2 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2023-3401 2 Aug 2023 < 16.0.8; 16.1.0 < 16.1.3; 16.2.0 < 16.2.2 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2023-4011 2 Aug 2023 15.11 < 16.2.2 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2023-3500 2 Aug 2023 10.0 < 16.0.8; 16.1 < 16.1.3; 16.2 < 16.2.2 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2023-3900 2 Aug 2023 16.1 < 16.1.3; 16.2 < 16.2.2 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2023-3993 2 Aug 2023 14.3 < 16.0.8; 16.1 < 16.1.3; 16.2 < 16.2.2 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2023-3994 2 Aug 2023 9.3 < 16.0.8; 16.1 < 16.1.3; 16.2 < 16.2.2 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2023-0632 1 Aug 2023 15.2 < 16.0.8; 16.1.0 < 16.1.3; 16.2.0 < 16.2.2 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2023-1210 1 Aug 2023 12.9 < 16.0.8; 16.1.0 < 16.1.3; 16.2.0 < 16.2.2 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2023-2164 1 Aug 2023 15.9 < 16.0.8; 16.1.0 < 16.1.3; 16.2.0 < 16.2.2 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2023-3364 1 Aug 2023 8.14 < 16.0.8; 16.1 < 16.1.3; 16.2 < 16.2.2 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2023-3385 1 Aug 2023 8.10 < 16.0.8; 16.1.0 < 16.1.3; 16.2.0 < 16.2.2 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2023-1401 26 Jul 2023 3.0.29 < 4.0.5 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2023-3102 21 Jul 2023 16.0 < 16.0.6; 16.1 < 16.1.1 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2023-3484 21 Jul 2023 12.8 < 15.11.11; 16.0 < 16.0.7; 16.1 < 16.1.2 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2023-2620 13 Jul 2023 15.1 < 15.11.10; 16.0 < 16.0.6; 16.1 < 16.1.1 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2023-2576 13 Jul 2023 13.7 < 15.11.10; 16.0 < 16.0.6; 16.1 < 16.1.1 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2023-3362 13 Jul 2023 16.0 < 16.0.6; 16.1 < 16.1.1 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2023-3363 13 Jul 2023 13.6 < 15.11.10; 16.0 < 16.0.6; 16.1 < 16.1.1 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2023-3444 13 Jul 2023 15.3 < 15.11.10; 16.0 < 16.0.6; 16.1 < 16.1.1 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2023-3424 13 Jul 2023 10.3 < 15.11.10; 16.0 < 16.0.6; 16.1 < 16.1.1 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2023-2200 13 Jul 2023 7.14 < 15.11.10; 16.0 < 16.0.6; 16.1 < 16.1.1 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2023-2190 13 Jul 2023 13.10 < 15.11.10; 16.0 < 16.0.6; 16.1 < 16.1.1 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2023-1936 11 Jul 2023 13.7 < 15.11.10; 16.0 < 16.0.6; 16.1 < 16.1.1 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.