dbcve.org
GitLabApplication

CVE-2025-7659

CRITICAL · 9.1 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 →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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 CE/EE affecting all versions from 18.2 before 18.6.6, 18.7 before 18.7.4, and 18.8 before 18.8.4 that could have allowed an unauthenticated user to steal tokens and access private repositories by abusing incomplete validation in the Web IDE.

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

A vulnerability in the Web IDE component of GitLab CE/EE versions 18.2 through 18.6.5, 18.7.0-18.7.3, and 18.8.0-18.8.3 contains incomplete validation that allows unauthenticated attackers to steal session or API tokens and gain unauthorized access to private repositories.

MitigationUpgrade GitLab to version 18.6.6, 18.7.4, 18.8.4 or later to remediate this vulnerability.

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.2.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
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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 `sudo gitlab-rake gitlab:env:info` or `sudo gitlab-ctl version` to retrieve the installed GitLab version
    Affected if Version is 18.2.0 through 18.6.5, 18.7.0 through 18.7.3, or 18.8.0 through 18.8.3
  2. Verify Web IDE component is enabled
    Check the GitLab configuration file (usually /etc/gitlab/gitlab.rb) for the Web IDE setting, or run `sudo gitlab-ctl config-check` to verify feature flags
    Affected if Web IDE feature is enabled on the instance
  3. Confirm instance accessibility
    Review the GitLab external URL configuration and network exposure to determine if the instance accepts unauthenticated requests
    Affected if The GitLab instance is reachable by unauthenticated users over HTTP/HTTPS

If the installed GitLab version falls within 18.2.0-18.6.5, 18.7.0-18.7.3, or 18.8.0-18.8.3 AND the Web IDE component is enabled AND the instance accepts unauthenticated access, the environment is affected by this vulnerability.

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 to version 18.6.6, 18.7.4, 18.8.4 or later to remediate this vulnerability.

Recommended fix High confidence

Upgrade to 18.6.6 (or later 18.6.x), 18.7.4 (or later 18.7.x), or 18.8.4 (or later 18.8.x) - prefer the latest stable release in your minor version branch

  1. Identify your current GitLab version by checking the GitLab admin area or running `gitlab-rake gitlab:env:info`
  2. Review the GitLab upgrade documentation for your current version to understand the upgrade path
  3. Plan for a maintenance window as upgrade will require service downtime
  4. Back up your GitLab database and repositories before proceeding
  5. For Helm deployments (GitLab Kubernetes): run `helm repo update` and then `helm upgrade` to the desired version
  6. For Omnibus installations: download and install the appropriate package for your OS from GitLab's packages repository
  7. For source installations: clone the desired version tag and follow the installation from source guide
  8. After upgrade, verify the GitLab version matches the target: `gitlab-rake gitlab:env:info`
Caveat Standard GitLab upgrade considerations apply (review release notes for deprecations and breaking changes between your current and target version)

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

Fix this in GitLab Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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