dbcve.org
GitLabApplication

CVE-2025-2443

MEDIUM · 6.1 CVSS v3.1 Published 2025-06-20
Fix available
A fix is available. Upgrade to 17.9.7 / 17.10.5 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 EE that allows for cross-site-scripting attack and content security policy bypass in a user's browser under specific conditions, affecting all versions from 16.6 before 17.9.7, 17.10 before 17.10.5, and 17.11 before 17.11.1.

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

GitLab EE contains a stored cross-site-scripting (XSS) vulnerability combined with a content security policy bypass that allows attackers to execute arbitrary JavaScript in victim browsers under specific conditions. The vulnerability affects versions 16.6 through 17.11.0 and exists in the web interface.

MitigationUpgrade GitLab EE to version 17.9.7, 17.10.5, 17.11.1 or later. These versions contain patches for the XSS and CSP bypass. Alternatively, implement strict CSP headers and sanitize user inputs as a temporary mitigation.

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.6.0, < 17.9.7>= 17.10.0, < 17.10.5= 17.11.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
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. Check GitLab version in admin dashboard
    Log in as an administrator, navigate to the Admin Area, then go to the 'Help' or 'Overview' section to view the running GitLab version
    Affected if The version displayed is 16.6.0 through 17.9.6, 17.10.0 through 17.10.4, or exactly 17.11.0
  2. Check GitLab version via command line
    On the GitLab server, run `gitlab-rake gitlab:env:info` or check the `/opt/gitlab/version` file to obtain the exact installed version
    Affected if The reported version falls within the affected ranges: >= 16.6.0 and < 17.9.7, or >= 17.10.0 and < 17.10.5, or = 17.11.0
  3. Verify web interface is in use
    Confirm that the GitLab web interface is accessible and actively used; this vulnerability affects the web interface functionality
    Affected if The web interface is accessible and users interact with it, as the XSS vulnerability exists in web-facing components

You are affected if your GitLab EE installation runs version 16.6.0 through 17.9.6, 17.10.0 through 17.10.4, or exactly 17.11.0 and the web interface is accessible.

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.9.7 / 17.10.5 or later
Fixed in 17.9.717.10.5
Interim mitigation

Upgrade GitLab EE to version 17.9.7, 17.10.5, 17.11.1 or later. These versions contain patches for the XSS and CSP bypass. Alternatively, implement strict CSP headers and sanitize user inputs as a temporary mitigation.

Recommended fix High confidence

17.11.1 (or latest 17.11.x release)

  1. 1. Backup your GitLab instance data and configuration
  2. 2. Check your current GitLab version in Admin Area > Overview > Dashboard
  3. 3. For Debian/Ubuntu: Update your apt sources and run `sudo apt-get update && sudo apt-get install gitlab-ee`
  4. 4. For RHEL/CentOS: Run `sudo yum install gitlab-ee`
  5. 5. Run `sudo gitlab-ctl reconfigure` to apply configuration changes
  6. 6. Run `sudo gitlab-ctl restart` to ensure all services restart with new version
  7. 7. Verify the upgrade was successful by checking the version in Admin Area > Overview > Dashboard
Caveat Review GitLab 17.x release notes for any deprecated features or breaking changes before upgrading, especially if upgrading from 16.x

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
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
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,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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