GitLabApplication
CVE-2025-0555
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 · uneditedA Cross Site Scripting (XSS) vulnerability in GitLab-EE affecting all versions from 16.6 prior to 17.7.6, 17.8 prior to 17.8.4, and 17.9 prior to 17.9.1 allows an attacker to bypass security controls and execute arbitrary scripts in a users browser under specific conditions.
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 confidenceCross Site Scripting (XSS) vulnerability in GitLab Enterprise Edition allows attackers to bypass existing security controls and execute arbitrary JavaScript in authenticated users' browsers, exploiting specific conditions within the affected versions.
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
>= 16.6.0, < 17.7.6>= 17.8.0, < 17.8.4= 17.9.0CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Check GitLab versionRun command: `sudo gitlab-rake gitlab:version` or check `/opt/gitlab/embedded/service/gitlab-rails/VERSION`Affected if Version is < 17.7.6, or between 17.8.0 and 17.8.4 inclusive, or exactly 17.9.0
-
Confirm GitLab edition is Enterprise EditionRun command: `sudo gitlab-rake gitlab:env:info` and look for 'GitLab Enterprise Edition' in the output, or check the license file at `/var/opt/gitlab/gitlab-rails/etc/gitlab-license.toml`Affected if Instance is GitLab Enterprise Edition (the vulnerability only affects EE, not CE)
-
Verify authentication is enabledConfirm the GitLab instance allows user authentication by accessing the web UI or checking `sudo gitlab-ctl status` shows unicorn/puma workers runningAffected if User authentication is enabled (the XSS targets authenticated users' browsers)
Your environment is affected if you are running GitLab Enterprise Edition version 16.6.0 or higher that falls within the affected ranges: < 17.7.6, 17.8.0-17.8.4, or exactly 17.9.0
Generated from the published advisory. Verify against your own configuration.
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 · scoped17.7.617.8.4
Upgrade GitLab-EE to version 17.7.6, 17.8.4, 17.9.1 or later to resolve the vulnerability.
Upgrade to 17.7.6, 17.8.4, or 17.9.1 (or later) - recommend 17.9.1 or latest stable 17.x release
- Identify your current GitLab version using the GitLab Rails console: `gitlab-rails runner 'puts Gitlab::VERSION' or check the GitLab admin area
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 / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-0555 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-0555 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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