CVE-2025-12575
📋 TL;DR
This vulnerability allows authenticated GitLab users with specific permissions to make unauthorized requests to internal network services through the GitLab server, potentially accessing internal systems. It affects GitLab EE versions 18.0-18.6.5, 18.7.0-18.7.3, and 18.8.0-18.8.3.
💻 Affected Systems
- GitLab EE
📦 What is this software?
Gitlab by Gitlab
GitLab is a complete DevOps platform providing source code management, CI/CD pipelines, security scanning, container registry, and collaboration tools used by millions of developers and thousands of enterprises worldwide. As both a cloud-hosted SaaS offering (GitLab.com) and self-managed software, G...
Learn more about Gitlab →Gitlab by Gitlab
GitLab is a complete DevOps platform providing source code management, CI/CD pipelines, security scanning, container registry, and collaboration tools used by millions of developers and thousands of enterprises worldwide. As both a cloud-hosted SaaS offering (GitLab.com) and self-managed software, G...
Learn more about Gitlab →Gitlab by Gitlab
GitLab is a complete DevOps platform providing source code management, CI/CD pipelines, security scanning, container registry, and collaboration tools used by millions of developers and thousands of enterprises worldwide. As both a cloud-hosted SaaS offering (GitLab.com) and self-managed software, G...
Learn more about Gitlab →⚠️ Risk & Real-World Impact
Worst Case
An attacker could pivot through GitLab to access sensitive internal services, potentially compromising internal systems or exfiltrating data.
Likely Case
Limited internal service enumeration or data exposure from services accessible to the GitLab server.
If Mitigated
Minimal impact with proper network segmentation and GitLab server isolation from sensitive internal services.
🎯 Exploit Status
Requires authenticated access and specific permissions. CWE-918 indicates Server-Side Request Forgery (SSRF) vulnerability.
🛠️ Fix & Mitigation
✅ Official Fix
Patch Version: 18.6.6, 18.7.4, or 18.8.4
Vendor Advisory: https://about.gitlab.com/releases/2026/02/10/patch-release-gitlab-18-8-4-released/
Restart Required: Yes
Instructions:
1. Backup your GitLab instance. 2. Update to GitLab EE 18.6.6, 18.7.4, or 18.8.4 using your preferred update method (Omnibus, Helm, source). 3. Restart GitLab services.
🔧 Temporary Workarounds
Network Segmentation
allRestrict GitLab server's network access to only required internal services
Permission Review
allReview and restrict user permissions to minimize attack surface
🧯 If You Can't Patch
- Implement strict network segmentation to isolate GitLab from sensitive internal services
- Review and minimize user permissions, especially for users who could potentially exploit this vulnerability
🔍 How to Verify
Check if Vulnerable:
Check GitLab version: sudo gitlab-rake gitlab:env:info | grep 'GitLab version'Check Version:
sudo gitlab-rake gitlab:env:info | grep 'GitLab version'Verify Fix Applied:
Confirm version is 18.6.6, 18.7.4, or 18.8.4 or higher📡 Detection & Monitoring
Log Indicators:
- Unusual outbound requests from GitLab to internal services
- SSRF-related error messages in logs
Network Indicators:
- Unexpected traffic from GitLab server to internal services not typically accessed
SIEM Query:
source="gitlab" AND (http_request_to_internal_network OR ssrf_attempt)