# CVE-2023-5612: Missing Authorization in GitLab

> Attackers can read user email addresses via tags feed even when profile visibility is disabled, exposing private user data.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 26 Jan 2024
- **Updated:** 14 Aug 2026
- **Also known as:** BIT-gitlab-2023-5612, GHSA-g884-f5hg-pgw8, UBUNTU-CVE-2023-5612

## What is CVE-2023-5612?

CVE-2023-5612 is a medium-severity missing authorization vulnerability in Gitlab Gitlab, published on 26 Jan 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An issue has been discovered in GitLab affecting all versions before 16.6.6, 16.7 prior to 16.7.4, and 16.8 prior to 16.8.1. It was possible to read the user email address via tags feed although the visibility in the user profile has been disabled.

Weakness: CWE-862 (Missing Authorization)

## Which versions are affected by CVE-2023-5612?

1 open source package ship an affected version, including gitlab. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `gitlab` | Bitnami | All versions | 16.6.6, 16.7.4, 16.8.1 |

Products: Gitlab Gitlab.

## How do I fix CVE-2023-5612?

Upgrade gitlab to a fixed version for your release line: 16.6.6, 16.7.4 or 16.8.1.

## Is CVE-2023-5612 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-5612 exists.

Public exploit code:

- GitLab Tags RSS feed email disclosure (metasploit)
- Analysis via script CVE-2023-5612 (github_poc): https://github.com/ConstantineFedorov/Review.CVE-2023-5612
- Nmap NSE to check for CVE-2023-5612 (github_poc): https://github.com/mad3E7cat/CVE-2023-5612

## Other vulnerabilities in Gitlab Gitlab

- [CVE-2026-97229](https://insights.sbomify.com/CVE-2026-97229/): GitLab Community Edition and Enterprise Edition Integer Overflow or Wraparound (critical 10.0, exploited in the wild)
- [CVE-2026-85706](https://insights.sbomify.com/CVE-2026-85706/): GitLab Community Edition and Enterprise Edition Path Traversal (critical 10.0, exploited in the wild)
- [CVE-2023-7028](https://insights.sbomify.com/CVE-2023-7028/): GitLab Community and Enterprise Editions Improper Access Control (critical 10.0, exploited in the wild)
- [CVE-2021-22205](https://insights.sbomify.com/CVE-2021-22205/): GitLab Community and Enterprise Editions Remote Code Execution (critical 10.0, exploited in the wild)
- [CVE-2021-39935](https://insights.sbomify.com/CVE-2021-39935/): GitLab Community and Enterprise Editions Server-Side Request Forgery (SSRF) (medium 6.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-5612 and fix it if it is affected.

What it is: CVE-2023-5612 is a medium-severity missing authorization vulnerability in Gitlab Gitlab, published on 26 Jan 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-5612 exists.

Affected packages and fixed versions:
- gitlab (Bitnami): affected all versions; fixed in 16.6.6, 16.7.4, 16.8.1

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2023-5612/ (Markdown: https://insights.sbomify.com/CVE-2023-5612/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2023-5612
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2023-5612
- OSV: https://osv.dev/vulnerability/CVE-2023-5612

---
From sbomify Insights: https://insights.sbomify.com/CVE-2023-5612/
Summaries are generated and may contain mistakes; the official description above is the record.