● Branch of GitLab
GitLab 16.0
GitLab 16.0 reached end of life on 22 August 2023. Move to 19.4.10 or newer.
Data: .
Fix releases of GitLab 16.0
| Release | Fixes | Signs of exploitation |
|---|---|---|
| 16.0.8 | 13 CVE records that this page reads | 1 record with EPSS 0.50 or more (CVE-2023-2164) among the records this page reads |
| 16.0.7 | 1 CVE record that this page reads | none among the records this page reads |
| 16.0.6 | 10 CVE records that this page reads | none among the records this page reads |
| 16.0.2 | 12 CVE records that this page reads | 2 records with EPSS 0.50 or more (CVE-2023-0921 and CVE-2023-2442) among the records this page reads |
Records with no fixed release for 16.0
These records name the branch as affected and name no release that ends the range.
| Record | Signs of exploitation | Fixed in |
|---|---|---|
| CVE-2023-2825An issue has been discovered in GitLab CE/EE affecting only version 16.0.0. An unauthenticated malicious user can use a path traversal vulnerability to read arbitrary files on the server when an…10.0 Critical · published 26 May 2023 | Metasploit module EPSS 0.50 or more | The record names no fixed release for 16.0. |
GitLab 16.0 in dates
| What | When |
|---|---|
| Released | 18 May 2023 |
| Bug and security fixes end | 22 June 2023 |
| End of life | 22 August 2023 |
| Newest release | 16.0.10 (23 September 2024) |
What this page says
The lifecycle data lists 16.0.10 (23 September 2024) for GitLab 16.0, after its end of life on 22 August 2023. This page cannot tell whether that release fixes anything.
This page reads 649 CVE records that the CVE Numbering Authorities GitLab and HackerOne have published since 22 August 2023 and that name GitLab. 3 of them are not placed on a branch (the page of the platform counts why). Of the others, none gives a range of its own for GitLab 16.0, and 336 give a range that reaches back into GitLab 16.0 and ends in a newer branch; as the record states it, that range holds releases of GitLab 16.0.
No release of GitLab 16.0 is called safe here, because the branch has ended, whatever the records say of it.
A release is the fix of a record when the record's affected range for this branch ends before it. Dates are from the product lifecycle data credited under Sources.
Sources
- CVE records: Copyright © 1999-2026, The MITRE Corporation. CVE is a trademark and the CVE logo is a registered trademark of The MITRE Corporation (source). Licence: CVE Program Terms of Use
- Product lifecycle dates from endoflife.date, Copyright 2020 endoflife.date contributors (MIT License) (source). Licence: MIT License
- EPSS scores by FIRST (https://www.first.org/epss/), generated by Empirical Security (source)