dbcve.org
GitLabApplication

CVE-2025-13761

CRITICAL · 9.6 CVSS v3.1 Published 2026-01-09
Fix available
A fix is available. Upgrade to 18.6.3 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges

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.6 before 18.6.3, and 18.7 before 18.7.1 that could have allowed an unauthenticated user to execute arbitrary code in the context of an authenticated user's browser by convincing the legitimate user to visit a specially crafted webpage.

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

Cross-site scripting (XSS) vulnerability in GitLab CE/EE versions 18.6.x before 18.6.3 and 18.7.x before 18.7.1 allows unauthenticated attackers to inject malicious JavaScript that executes in authenticated users' browsers via social engineering (convincing users to visit a crafted webpage), potentially enabling session hijacking and account takeover.

MitigationUpgrade GitLab to version 18.6.3, 18.7.1, or later. Review user sessions and consider rotating credentials if exploitation is suspected, as the attack targets authenticated user browser contexts.

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.6.0, < 18.6.3= 18.7.0

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
Required
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/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 'sudo gitlab-rake gitlab:env:info' or check the GitLab Admin Area > Settings > General page for the version number
    Affected if The installed version is 18.6.0, 18.6.1, 18.6.2, or 18.7.0
  2. Verify GitLab package version
    Run 'dpkg -l | grep gitlab-ce' (Debian/Ubuntu) or 'rpm -qa | grep gitlab' (RHEL/CentOS) to see the exact installed package version
    Affected if The package version matches any of the affected versions listed above
  3. Check GitLab rubygems version
    Run 'sudo gitlab-rake gems:env' or inspect /opt/gitlab/version-manifest.json to confirm the embedded package versions
    Affected if The GitLab core version corresponds to 18.6.0-18.6.2 or 18.7.0

You are affected if your GitLab installation runs any version from 18.6.0 through 18.6.2, or exactly version 18.7.0, as these versions contain the vulnerable code that allows stored XSS injection.

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.3 or later
Fixed in 18.6.3
Interim mitigation

Upgrade GitLab to version 18.6.3, 18.7.1, or later. Review user sessions and consider rotating credentials if exploitation is suspected, as the attack targets authenticated user browser contexts.

Recommended fix High confidence

18.6.3 or 18.7.1 (or later stable release)

  1. 1. Back up your GitLab instance data, including the database and repositories
  2. 2. For Debian/Ubuntu systems: Run `sudo apt-get update` and `sudo apt-get install gitlab-ce` (or `gitlab-ee`) to fetch the latest packages
  3. 3. For RHEL/CentOS systems: Run `sudo yum install gitlab-ce` (or `gitlab-ee`) to install the updated packages
  4. 4. Run `sudo gitlab-ctl reconfigure` to apply the configuration changes
  5. 5. Verify the upgrade was successful by checking the GitLab version with `sudo gitlab-rake gitlab:env:info`
  6. 6. Confirm the installed version is 18.6.3 or 18.7.1 (or later) using `sudo gitlab-rake gitlab:version`

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
  • Testing6.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,380
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,808.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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