dbcve.org
GitLabApplication

CVE-2025-2254

MEDIUM · 6.1 CVSS v3.1 Published 2025-06-12
Fix available
A fix is available. Upgrade to 17.10.8 / 17.11.4 or later.
See remediation →
68/100
Remediation priority · Elevated
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
An issue has been discovered in GitLab CE/EE affecting all versions from 17.9 before 17.10.8, 17.11 before 17.11.4, and 18.0 before 18.0.2. Improper output encoding in the snipper viewer functionality lead to Cross-Site scripting attacks.

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 stored Cross-Site Scripting (XSS) vulnerability in GitLab's snippet viewer functionality. The issue stems from improper output encoding, where malicious scripts embedded in snippets are not properly sanitized before rendering in the web interface. An attacker with low privileges (ability to create/modify snippets) can inject malicious JavaScript that executes when other users view the affected snippet.

MitigationUpgrade GitLab to version 17.10.8, 17.11.4, or 18.0.2 or later to receive the patch for 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:>= 17.9.0, < 17.10.8>= 17.11.0, < 17.11.4>= 18.0.0, < 18.0.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
None
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/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. Identify installed GitLab version
    Run command: gitlab-rake gitlab:env:info or check the GitLab admin dashboard under Help > Version. Alternatively, check /opt/gitlab/version on the server.
    Affected if The displayed version falls within 17.9.0 to 17.10.7, 17.11.0 to 17.11.3, or 18.0.0 to 18.0.1.
  2. Confirm snippet feature is accessible
    Log into GitLab as a low-privilege user (reporter or guest role) and verify access to the Snippets section in the user menu or project sidebar. Check if the /snippets endpoint responds.
    Affected if The snippet viewer functionality is available and the user can view snippets.
  3. Review existing snippets for unsanitized content
    Navigate to the Snippets section in the GitLab interface or query the database table snippets for records containing script tags, javascript:, or event handlers like onload/onerror in the content field.
    Affected if Any snippet contains raw HTML, script tags, or JavaScript event handlers that would execute when viewed.
  4. Check audit logs for snippet creation activity
    Access GitLab admin area under Monitor > Audit Events or use the API endpoint /api/v4/audit_events?entity_type=snippet to list snippet-related events.
    Affected if Audit logs show snippet creation from users with low privileges, or content that appears to be XSS payloads.

A user is affected if their GitLab instance runs a version within the ranges 17.9.0-17.10.7, 17.11.0-17.11.3, or 18.0.0-18.0.1 and the snippet feature is enabled for any user to view content.

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 17.10.8 / 17.11.4 / 18.0.2 or later
Fixed in 17.10.817.11.418.0.2
Interim mitigation

Upgrade GitLab to version 17.10.8, 17.11.4, or 18.0.2 or later to receive the patch for this vulnerability.

Recommended fix High confidence

Upgrade to 17.10.8 (if on 17.9.x), 17.11.4 (if on 17.11.x), or 18.0.2 (if on 18.0.x) - prefer the latest patch version in your minor line

  1. 1. Identify your current GitLab version by running `sudo gitlab-rake gitlab:env:info` or checking the GitLab admin area.
  2. 2. Determine your upgrade path based on your current version: if you're on 17.9.x, upgrade to 17.10.8; if on 17.11.x, upgrade to 17.11.4; if on 18.0.x, upgrade to 18.0.2.
  3. 3. Back up your GitLab data and configuration before upgrading.
  4. 4. For omnibus installations, run `sudo apt-get update && sudo apt-get install gitlab-ce` (or gitlab-ee for Enterprise).
  5. 5. For source installations, follow the upgrade instructions in GitLab documentation for your specific version.
  6. 6. After upgrade, verify GitLab is running: `sudo gitlab-ctl status`.
  7. 7. Clear browser cache to ensure the patched code loads properly.
Caveat Standard GitLab patch upgrades typically have minimal breaking changes; review GitLab release notes for any deprecation notices

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

Fix this in GitLab Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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