GitLab Security Release: 16.3.1, 16.2.5, and 16.1.5
On August 31, 2023, we released versions 16.3.1, 16.2.5 and 16.1.5 for GitLab Community Edition (CE) and Enterprise Edition (EE). These versions contain important security fixes, and we strongly recommend that all GitLab installations be upgraded to one of these versions immediately. GitLab.com is already running the patched version. GitLab releases patches for vulnerabilities in dedicated security releases. There are two types of security releases: a monthly, scheduled security release, released a week after the feature release (which deploys on the 22nd of each month), and ad-hoc security releases for critical vulnerabilities. For more information, you can visit our security FAQ . You can see all of our regular and security release blog posts here . In addition, the issues detailing each vulnerability are made public on our issue tracker 30 days after the release in which they were patched. We are dedicated to ensuring all aspects of GitLab that are exposed to customers or that host customer data are held to the highest security standards. As part of maintaining good security hygiene, it is highly recommended that all customers upgrade to the latest security release for their supported version. You can read more best practices in securing your GitLab instance in our blog post. Recommended Action We strongly recommend that all installations running a version affected by the issues described below are upgraded to the latest version as soon as possible . When no specific deployment type (omnibus, source code, helm chart, etc.) of a product is mentioned, this means all types are affected. Table of Fixes Title Severity Privilege escalation of “external user” to internal access through group service account medium Maintainer can leak sentry token by changing the configured URL (fix bypass) medium Google Cloud Logging private key showed in plain text in GitLab UI leaking to other group owners medium Information disclosure via project import endpoint medium Developer can
Details
Original advisory: https://docs.gitlab.com/releases/patches/patch-release-gitlab-16-3-1-released/
Exploitation outlook
EPSS (FIRST.org) estimates each CVE’s probability of exploitation in the next 30 days — here is the CSIRTS.com read on those numbers.
- Low exploitation riskCVE-2023-39150.56% 30-day exploitation probability — currently an unlikely target, but scores change as exploit code circulates. Riskier than 43% of all scored CVEs.
- Low exploitation riskCVE-2022-43650.71% 30-day exploitation probability — currently an unlikely target, but scores change as exploit code circulates. Riskier than 49% of all scored CVEs.
- Low exploitation riskCVE-2023-43780.43% 30-day exploitation probability — currently an unlikely target, but scores change as exploit code circulates. Riskier than 35% of all scored CVEs.
- Low exploitation riskCVE-2023-39500.21% 30-day exploitation probability — currently an unlikely target, but scores change as exploit code circulates. Riskier than 12% of all scored CVEs.
- Low exploitation riskCVE-2023-46300.40% 30-day exploitation probability — currently an unlikely target, but scores change as exploit code circulates. Riskier than 32% of all scored CVEs.
- Low exploitation riskCVE-2022-43430.39% 30-day exploitation probability — currently an unlikely target, but scores change as exploit code circulates. Riskier than 31% of all scored CVEs.
- Low exploitation riskCVE-2023-40180.39% 30-day exploitation probability — currently an unlikely target, but scores change as exploit code circulates. Riskier than 31% of all scored CVEs.
- Low exploitation riskCVE-2023-32050.70% 30-day exploitation probability — currently an unlikely target, but scores change as exploit code circulates. Riskier than 49% of all scored CVEs.
- Low exploitation riskCVE-2023-46470.61% 30-day exploitation probability — currently an unlikely target, but scores change as exploit code circulates. Riskier than 45% of all scored CVEs.
Referenced CVEs
| CVE | CSIRTS overview | External |
|---|---|---|
| CVE-2023-3915 | coverage & exploitation status | NVD · CVE.org |
| CVE-2022-4365 | coverage & exploitation status | NVD · CVE.org |
| CVE-2023-4378 | coverage & exploitation status | NVD · CVE.org |
| CVE-2023-3950 | coverage & exploitation status | NVD · CVE.org |
| CVE-2023-4630 | coverage & exploitation status | NVD · CVE.org |
| CVE-2022-4343 | coverage & exploitation status | NVD · CVE.org |
| CVE-2023-4638 | coverage & exploitation status | NVD · CVE.org |
| CVE-2023-4018 | coverage & exploitation status | NVD · CVE.org |
| CVE-2023-3205 | coverage & exploitation status | NVD · CVE.org |
| CVE-2023-4647 | coverage & exploitation status | NVD · CVE.org |
| CVE-2023-1279 | coverage & exploitation status | NVD · CVE.org |
| CVE-2023-0120 | coverage & exploitation status | NVD · CVE.org |
| CVE-2023-1555 | coverage & exploitation status | NVD · CVE.org |
More from GitLab Security Releases
- criticalGitLab Patch Release: 19.1.2, 19.0.4, 18.11.72026-07-08
- unknownGitLab Patch Release: 18.8.112026-07-01
- unknownGitLab patch release notes2026-07-01
- criticalGitLab Patch Release: 19.1.1, 19.0.3, 18.11.62026-06-24
- criticalGitLab Patch Release: 19.0.2, 18.11.5, 18.10.82026-06-10