GitLab Security Release: 16.2.2, 16.1.3, and 16.0.8
On August 1, 2023, we released versions 16.2.2, 16.1.3, and 16.0.8 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 ReDoS via ProjectReferenceFilter in any Markdown fields high ReDoS via AutolinkFilter in any Markdown fields high An attacker can run pipeline jobs as arbitrary user high Regex DoS in Harbor Registry search medium Arbitrary read of files owned by the “git” user via malicious tar.gz file upload using GitLab export functionality medium Stored XSS in Web ID
Details
Original advisory: https://docs.gitlab.com/releases/patches/patch-release-gitlab-16-2-2-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-39940.82% 30-day exploitation probability — currently an unlikely target, but scores change as exploit code circulates. Riskier than 53% of all scored CVEs.
- Elevated exploitation riskCVE-2023-336444.7% 30-day exploitation probability — well above the norm. Schedule remediation this cycle. Riskier than 99% of all scored CVEs.
- Low exploitation riskCVE-2023-39320.88% 30-day exploitation probability — currently an unlikely target, but scores change as exploit code circulates. Riskier than 55% of all scored CVEs.
- Low exploitation riskCVE-2023-06320.79% 30-day exploitation probability — currently an unlikely target, but scores change as exploit code circulates. Riskier than 52% of all scored CVEs.
- Low exploitation riskCVE-2023-33850.73% 30-day exploitation probability — currently an unlikely target, but scores change as exploit code circulates. Riskier than 50% of all scored CVEs.
- Exploitation likely imminentCVE-2023-2164EPSS puts this in the most-targeted tier (63.8% 30-day exploitation probability). Prioritize alongside KEV items. Riskier than 99% of all scored CVEs.
- Low exploitation riskCVE-2023-40020.49% 30-day exploitation probability — currently an unlikely target, but scores change as exploit code circulates. Riskier than 39% of all scored CVEs.
- Low exploitation riskCVE-2023-40080.60% 30-day exploitation probability — currently an unlikely target, but scores change as exploit code circulates. Riskier than 45% of all scored CVEs.
- Low exploitation riskCVE-2023-39930.61% 30-day exploitation probability — currently an unlikely target, but scores change as exploit code circulates. Riskier than 45% of all scored CVEs.
- Low exploitation riskCVE-2023-35000.47% 30-day exploitation probability — currently an unlikely target, but scores change as exploit code circulates. Riskier than 38% of all scored CVEs.
Referenced CVEs
| CVE | CSIRTS overview | External |
|---|---|---|
| CVE-2023-3994 | coverage & exploitation status | NVD · CVE.org |
| CVE-2023-3364 | coverage & exploitation status | NVD · CVE.org |
| CVE-2023-3932 | coverage & exploitation status | NVD · CVE.org |
| CVE-2023-0632 | coverage & exploitation status | NVD · CVE.org |
| CVE-2023-3385 | coverage & exploitation status | NVD · CVE.org |
| CVE-2023-2164 | coverage & exploitation status | NVD · CVE.org |
| CVE-2023-4002 | coverage & exploitation status | NVD · CVE.org |
| CVE-2023-4008 | coverage & exploitation status | NVD · CVE.org |
| CVE-2023-3993 | coverage & exploitation status | NVD · CVE.org |
| CVE-2023-3500 | coverage & exploitation status | NVD · CVE.org |
| CVE-2023-3401 | coverage & exploitation status | NVD · CVE.org |
| CVE-2023-3900 | coverage & exploitation status | NVD · CVE.org |
| CVE-2023-2022 | coverage & exploitation status | NVD · CVE.org |
| CVE-2023-4011 | coverage & exploitation status | NVD · CVE.org |
| CVE-2023-1210 | coverage & exploitation status | NVD · CVE.org |
Same CVEs, other sources
How other CERTs, PSIRTs and databases cover the vulnerabilities in this advisory.
- criticalGitLab Security Release: 16.6.1, 16.5.3, 16.4.3gitlab
- criticalGitLab Critical Security Release: 16.3.4 and 16.2.7gitlab
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