CVE-2025-12575
Server-Side Request Forgery in GitLab EE Allowing Internal Access
Publication date: 2026-02-11
Last updated on: 2026-02-13
Assigner: GitLab Inc.
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| gitlab | gitlab | From 18.7.0 (inc) to 18.7.4 (exc) |
| gitlab | gitlab | From 18.8.0 (inc) to 18.8.4 (exc) |
| gitlab | gitlab | From 18.0.0 (inc) to 18.6.6 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-918 | The web server receives a URL or similar request from an upstream component and retrieves the contents of this URL, but it does not sufficiently ensure that the request is being sent to the expected destination. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
CVE-2025-12575 is a Server-Side Request Forgery (SSRF) vulnerability in GitLab Enterprise Edition (EE). It affects versions from 18.0 up to but not including 18.6.6, 18.7 before 18.7.4, and 18.8 before 18.8.4. This vulnerability exists in the Virtual Registry component of GitLab EE and could allow an authenticated user with certain permissions to make unauthorized requests to internal network services through the GitLab server.
How can this vulnerability impact me? :
This vulnerability can allow an authenticated user with limited permissions to perform SSRF attacks, which means they could send unauthorized requests to internal network services via the GitLab server. This could lead to partial compromise of confidentiality and integrity of internal services, potentially exposing sensitive data or allowing manipulation of internal resources. However, it does not impact availability.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
I don't know
How can this vulnerability be detected on my network or system? Can you suggest some commands?
I don't know
What immediate steps should I take to mitigate this vulnerability?
To mitigate the CVE-2025-12575 vulnerability, it is strongly recommended to upgrade all self-managed GitLab Enterprise Edition (EE) installations to the patched versions.
- Upgrade to GitLab EE version 18.6.6 or later if you are running any version from 18.0 before 18.6.6.
- Upgrade to GitLab EE version 18.7.4 or later if you are running any version 18.7 before 18.7.4.
- Upgrade to GitLab EE version 18.8.4 or later if you are running any version 18.8 before 18.8.4.
These upgrades address the Server-Side Request Forgery (SSRF) vulnerability in the Virtual Registry component that could allow an authenticated user with certain permissions to make unauthorized requests to internal network services.