dbcve.org
GitLabApplication

CVE-2025-0475

MEDIUM · 6.1 CVSS v3.1 Published 2025-03-03
Fix available
A fix is available. Upgrade to 17.7.6 / 17.8.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 15.10 prior to 17.7.6, 17.8 prior to 17.8.4, and 17.9 prior to 17.9.1. A proxy feature could potentially allow unintended content rendering leading to XSS under specific circumstances.

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

An XSS vulnerability exists in GitLab CE/EE's proxy feature that allows unintended content rendering. The vulnerability requires specific circumstances to exploit and affects versions from 15.10 through 17.9 (prior to patched releases). The CVSS 6.1 indicates moderate severity typically requiring some user interaction or specific conditions.

MitigationUpgrade GitLab to version 17.7.6, 17.8.4, or 17.9.1 or later to receive the security patch for this XSS vulnerability in the proxy feature.

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:>= 15.10.0, < 17.7.6>= 17.8.0, < 17.8.4= 17.9.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. Identify installed GitLab version
    Run `sudo gitlab-rake gitlab:version` or check the GitLab admin panel under Help > Version. Alternatively, check the /opt/gitlab/version-oss file on the GitLab server.
    Affected if The version output matches: 15.10.x through 17.7.5, 17.8.0 through 17.8.3, or exactly 17.9.0
  2. Confirm GitLab component type
    Verify this is a GitLab CE (Community Edition) or EE (Enterprise Edition) installation, as the vulnerability affects these editions.
    Affected if The installation is GitLab CE or EE (not GitLab Runner or other components alone)
  3. Check if proxy feature is configured
    Review GitLab configuration files (typically /etc/gitlab/gitlab.rb) for proxy-related settings such as `proxy`, `http_proxy`, `https_proxy`, or any custom proxy middleware configurations under the gitlab_rails section.
    Affected if Proxy settings are actively configured in the GitLab environment; the vulnerability exists in the proxy feature itself

A user is affected if their GitLab CE/EE version falls within the affected ranges (15.10.0-17.7.5, 17.8.0-17.8.3, or 17.9.0) AND the proxy feature is enabled or configured in their environment.

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.7.6 / 17.8.4 or later
Fixed in 17.7.617.8.4
Interim mitigation

Upgrade GitLab to version 17.7.6, 17.8.4, or 17.9.1 or later to receive the security patch for this XSS vulnerability in the proxy feature.

Recommended fix High confidence

17.7.6, 17.8.4, or 17.9.1 (depending on your current branch)

  1. 1. Identify the current GitLab installation version using `gitlab-rake gitlab:env:info` or checking the Admin Area dashboard
  2. 2. Based on the current version, determine the appropriate upgrade path to a fixed release:
  3. - If running 15.10.x through 17.7.x: upgrade to 17.7.6 or later in the 17.7 branch
  4. - If running 17.8.x: upgrade to 17.8.4 or later in the 17.8 branch
  5. - If running 17.9.0: upgrade to 17.9.1 or later in the 17.9 branch
  6. 3. Review the GitLab upgrade documentation for your installation method (Omnibus or source)
  7. 4. Create a full backup of the GitLab instance before upgrading
  8. 5. Follow the standard GitLab upgrade procedure for your version jump
Caveat Major version upgrades between GitLab major releases may have breaking changes; review the GitLab release notes for your upgrade path

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-0475 — 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-0475 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