CVE-2025-1212 Exposure of Sensitive System Information to an Unauthorized Control Sphere in GitLab
An attacker can send crafted requests to reveal sensitive system information in GitLab, requiring an upgrade to secure the instance.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2025-1212?
CVE-2025-1212 is a medium-severity vulnerability in Gitlab Gitlab, published on 12 Feb 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Official description
An information disclosure vulnerability in GitLab CE/EE affecting all versions from 8.3 prior to 17.6.5, 17.7 prior to 17.7.4, and 17.8 prior to 17.8.2 allows an attacker to send a crafted request to a backend server to reveal sensitive information.
Weakness: CWE-497
Which versions are affected by CVE-2025-1212?
1 open source package ship an affected version, including gitlab. It affects 1 product.
| Package | Affected | Fixed in |
|---|---|---|
gitlab Bitnami | From 8.3.0 | 17.8.2 |
Products include Gitlab Gitlab.
How do I fix CVE-2025-1212?
Upgrade gitlab to 17.8.2 or later.
Is CVE-2025-1212 being exploited?
There is no known exploitation of CVE-2025-1212 in the wild and no public exploit code.
Other vulnerabilities in Gitlab Gitlab
- CVE-2026-97229 GitLab Community Edition and Enterprise Edition Integer Overflow or Wraparound
- CVE-2026-85706 GitLab Community Edition and Enterprise Edition Path Traversal
- CVE-2023-7028 GitLab Community and Enterprise Editions Improper Access Control
- CVE-2021-22205 GitLab Community and Enterprise Editions Remote Code Execution
- CVE-2021-39935 GitLab Community and Enterprise Editions Server-Side Request Forgery (SSRF)
Sources
Also known as BIT-gitlab-2025-1212, GHSA-68hg-5q58-g3cv, UBUNTU-CVE-2025-1212.