dbcve.org
GitLabApplication

CVE-2025-6454

HIGH · 8.8 CVSS v3.1 Published 2025-09-12
Fix available
A fix is available. Upgrade to 18.1.6 / 18.2.6 or later.
See remediation →
94/100
Remediation priority · Urgent
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
An issue has been discovered in GitLab CE/EE affecting all versions from 16.11 before 18.1.6, 18.2 before 18.2.6, and 18.3 before 18.3.2 that could have allowed authenticated users to make unintended internal requests through proxy environments by injecting crafted sequences.

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 CE/EE where authenticated users can inject crafted sequences into requests, enabling them to make the GitLab server perform unintended internal network requests through configured proxy environments. This could allow access to internal services, metadata endpoints, or infrastructure that should not be exposed.

MitigationUpgrade GitLab to version 18.1.6, 18.2.6, or 18.3.2 or later. If immediate patching is not possible, review and restrict proxy configurations and network access controls to limit potential internal reconnaissance.

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:>= 16.11.0, < 18.1.6>= 18.2.0, < 18.2.6>= 18.3.0, < 18.3.2

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
High
Integrity
High
Availability
High

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

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 visit the GitLab admin panel under Help > Version to determine the exact version number
    Affected if Version is 16.11.0 to 18.1.5, 18.2.0 to 18.2.5, or 18.3.0 to 18.3.1
  2. Verify proxy configuration exists
    Review /etc/gitlab/gitlab.rb for proxy settings such as `gitlab_rails['http_proxy']` or check environment variables (HTTP_PROXY, HTTPS_PROXY) available to GitLab processes
    Affected if An HTTP/HTTPS proxy is configured for GitLab outbound requests
  3. Confirm external webhook or integration features are accessible
    Check if any authenticated users have permissions to create or modify webhooks, service integrations, or import features that trigger outbound HTTP requests
    Affected if Authenticated users can configure webhooks or integrations that cause GitLab to make outbound requests
  4. Review network routing from GitLab server
    Examine routing tables, firewall rules, or cloud security groups to determine if the GitLab server can reach internal network ranges or metadata endpoints
    Affected if GitLab server has the ability to initiate connections to internal network addresses or cloud metadata services

The environment is affected if running a GitLab version within the vulnerable ranges AND the server is configured to use a proxy AND can reach internal network resources that could be targeted via SSRF.

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.1.6 / 18.2.6 / 18.3.2 or later
Fixed in 18.1.618.2.618.3.2
Interim mitigation

Upgrade GitLab to version 18.1.6, 18.2.6, or 18.3.2 or later. If immediate patching is not possible, review and restrict proxy configurations and network access controls to limit potential internal reconnaissance.

Recommended fix High confidence

18.3.2 (or 18.2.6/18.1.6 depending on your current version branch - recommend upgrading to 18.3.2 for latest fixes)

  1. 1. Back up your GitLab instance data and configuration before proceeding with the upgrade
  2. 2. Check your current GitLab version by running: gitlab-rake gitlab:env:info
  3. 3. For Ubuntu/Debian systems: sudo apt-get update && sudo apt-get install gitlab-ce=<version> or gitlab-ee=<version>
  4. 4. For RHEL/CentOS systems: sudo yum install gitlab-ce-<version> or gitlab-ee-<version>
  5. 5. Replace <version> with 18.1.6, 18.2.6, or 18.3.2 (choose the appropriate fixed version for your current version branch)
  6. 6. Run sudo gitlab-ctl reconfigure to apply the configuration changes
  7. 7. Verify the upgrade was successful by checking: gitlab-rake gitlab:env:info
  8. 8. Confirm the installed version shows the patched release (18.1.6, 18.2.6, or 18.3.2)
Caveat Review GitLab upgrade documentation for any breaking changes between your current version and target version; minor version upgrades typically have minimal breaking changes

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

Fix this in GitLab Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing6.0 h
  • Review / QA3.0 h
19.0 hours of engineering $3,320
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-6454 — 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-6454 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