dbcve.org
GitLabApplication

CVE-2025-12575

MEDIUM · 5.4 CVSS v3.1 Published 2026-02-11
Fix available
A fix is available. Upgrade to 18.6.6 / 18.7.4 or later.
See remediation →
60/100
Remediation priority · Elevated
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
GitLab has remediated an issue in GitLab EE affecting all versions from 18.0 before 18.6.6, 18.7 before 18.7.4, and 18.8 before 18.8.4 that, under certain conditions could have allowed an authenticated user with certain permissions to make unauthorized requests to internal network services through the GitLab server.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

This is a Server-Side Request Forgery (SSRF) vulnerability in GitLab Enterprise Edition. An authenticated user with certain permissions could exploit the GitLab server to make unauthorized requests to internal network services, effectively using the GitLab instance as a pivot point to attack internal infrastructure.

MitigationUpgrade GitLab EE to version 18.6.6 or later, 18.7.4 or later, or 18.8.4 or later. Additionally, apply network segmentation to restrict GitLab server access to only necessary internal services.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
GitLabApplication
Affected:>= 18.0.0, < 18.6.6>= 18.7.0, < 18.7.4>= 18.8.0, < 18.8.4

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check installed GitLab version
    Run `gitlab-rake gitlab:env:info` or access Help > Version in the GitLab web interface to display the running version number
    Affected if The displayed version falls within any of these ranges: >= 18.0.0 and < 18.6.6, OR >= 18.7.0 and < 18.7.4, OR >= 18.8.0 and < 18.8.4
  2. Confirm GitLab edition is Enterprise Edition
    Run `gitlab-rake gitlab:env:info` and look for the 'GitLab EE' designation, or check the web interface footer which displays either 'GitLab Enterprise Edition' or 'GitLab Community Edition'
    Affected if The instance is GitLab Enterprise Edition (EE) and the version is in the affected ranges listed above
  3. Identify if webhooks or integration features are accessible to non-admin users
    Review user role permissions in Admin Area > Users and Admin Area > Settings > General. Check if authenticated users with Reporter, Developer, or Maintainer roles can create or modify webhooks, service integrations, or import features
    Affected if Lower-privileged authenticated users have the ability to configure webhooks, CI/CD integrations, or import utilities that could be leveraged to trigger the SSRF
  4. Audit recent network-facing requests from GitLab
    Review GitLab logs at /var/log/gitlab/gitlab-rails/production.log for suspicious outbound requests to internal IP ranges (10.x.x.x, 192.168.x.x, 172.16-31.x.x) or internal hostnames, particularly from webhook or import endpoints
    Affected if Logs show GitLab server making outbound requests to internal network addresses that were not initiated by legitimate administrative functions

You are affected if your GitLab instance is Enterprise Edition running a version within 18.0.0 to 18.6.5, 18.7.0 to 18.7.3, or 18.8.0 to 18.8.3, and authenticated users have access to features that can trigger outbound network requests.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 18.6.6 / 18.7.4 / 18.8.4 or later
Fixed in 18.6.618.7.418.8.4
Interim mitigation

Upgrade GitLab EE to version 18.6.6 or later, 18.7.4 or later, or 18.8.4 or later. Additionally, apply network segmentation to restrict GitLab server access to only necessary internal services.

Recommended fix High confidence

18.6.6 (for 18.0-18.6.x), 18.7.4 (for 18.7.x), or 18.8.4 (for 18.8.x)

  1. 1. Identify your current GitLab installation version using `gitlab-rake gitlab:version`
  2. 2. Determine which upgrade path applies based on your current version (18.0-18.6.x → 18.6.6, 18.7.x → 18.7.4, or 18.8.x → 18.8.4)
  3. 3. Back up your GitLab instance database and repositories before upgrading
  4. 4. Follow the official GitLab upgrade documentation for your deployment method (Omnibus, source, or Helm chart)
  5. 5. Stop GitLab services before upgrade
  6. 6. Install the appropriate fixed version (18.6.6, 18.7.4, or 18.8.4)
  7. 7. Reconfigure GitLab: `gitlab-ctl reconfigure`
  8. 8. Verify the upgrade completed successfully: `gitlab-rake gitlab:git:fsck`
Caveat Review GitLab release notes for each intermediate version for potential configuration or behavior changes

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in GitLab Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-12575 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-12575 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data