dbcve.org
GitLabApplication

CVE-2025-6948

HIGH · 8.0 CVSS v3.1 Published 2025-07-10
Fix available
A fix is available. Upgrade to 17.11.6 / 18.0.4 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable

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.11 before 17.11.6, 18.0 before 18.0.4, and 18.1 before 18.1.2 that, under certain conditions, could have allowed a successful attacker to execute actions on behalf of users by injecting malicious content.

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 · moderate confidence

A content injection vulnerability in GitLab CE/EE allows authenticated attackers to inject malicious content that can be executed in the context of other users' sessions, enabling unauthorized actions to be performed on behalf of victim users. This appears to be a stored XSS or similar injection flaw affecting the web interface.

MitigationUpgrade GitLab to version 17.11.6, 18.0.4, or 18.1.2 or later. As a temporary measure, restrict user access and monitor for suspicious activity until patching is possible.

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.11.0, < 17.11.6>= 18.0.0, < 18.0.4>= 18.1.0, < 18.1.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
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/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. Identify installed GitLab version
    Run command: gitlab-rake gitlab:env:info or check the Admin Area > Settings > General page, or use the API endpoint /api/v4/version
    Affected if Version number falls within >= 17.11.0 to < 17.11.6, >= 18.0.0 to < 18.0.4, or >= 18.1.0 to < 18.1.2
  2. Verify GitLab is accessible via web interface
    Confirm the GitLab web interface is running and reachable
    Affected if Web interface is enabled and accessible to users
  3. Confirm user authentication is enabled
    Check that user registration or invitation features are active, or that existing user accounts exist
    Affected if Authenticated users can access the web interface and create or modify content
  4. Audit recent user-generated content for suspicious scripts
    Review recent issues, merge requests, comments, snippets, or wiki pages via Admin Area > Audit Events, or search for script tags in database: sudo gitlab-psql -d gitlabhq_production -c "SELECT * FROM notes WHERE note LIKE '%<script%' LIMIT 100;"
    Affected if Malicious script tags or encoded JavaScript payloads are found in user-submitted content

User is affected if their GitLab version is 17.11.0-17.11.5, 18.0.0-18.0.3, or 18.1.0-18.1.1 and the web interface with authenticated user access is enabled.

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.11.6 / 18.0.4 / 18.1.2 or later
Fixed in 17.11.618.0.418.1.2
Interim mitigation

Upgrade GitLab to version 17.11.6, 18.0.4, or 18.1.2 or later. As a temporary measure, restrict user access and monitor for suspicious activity until patching is possible.

Recommended fix High confidence

Upgrade to GitLab 17.11.6+, 18.0.4+, or 18.1.2+ (or latest stable in respective minor version)

  1. 1. Backup your GitLab instance before starting the upgrade process
  2. 2. Check your current GitLab version by running `gitlab-rake gitlab:env:info` or looking at the Admin Area > Settings > General
  3. 3. If running 17.11.x: upgrade to GitLab 17.11.6 or later (recommend latest 17.11.x patch)
  4. 4. If running 18.0.x: upgrade to GitLab 18.0.4 or later (recommend latest 18.0.x patch)
  5. 5. If running 18.1.x: upgrade to GitLab 18.1.2 or later (recommend latest 18.1.x patch)
  6. 6. Follow GitLab's standard upgrade instructions for your installation method (Omnibus, source, etc.)
  7. 7. After upgrade, verify the new version is running with `gitlab-rake gitlab:env:info`
  8. 8. Test that the application functions normally after the upgrade
Caveat Review GitLab release notes for any breaking changes between your current and target version; major version jumps may require additional migration steps

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
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
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,120.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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