dbcve.org
GitLabApplication

CVE-2026-0752

MEDIUM · 6.1 CVSS v3.1 Published 2026-02-25
Fix available
A fix is available. Upgrade to 18.7.5 / 18.8.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
GitLab has remediated an issue in GitLab CE/EE affecting all versions from 16.2 before 18.7.5, 18.8 before 18.8.5, and 18.9 before 18.9.1 that under certain circumstances, could have allowed an unauthenticated user to inject arbitrary scripts into the Mermaid sandbox UI.

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 cross-site scripting (XSS) vulnerability in GitLab's Mermaid diagram sandbox UI that allows unauthenticated users to inject arbitrary JavaScript scripts. The vulnerability affects GitLab CE/EE versions 16.2 through 18.7.4, 18.8.x through 18.8.4, and 18.9.x through 18.9.0.

MitigationGitLab has released patched versions (18.7.5, 18.8.5, 18.9.1 and later). Organizations should upgrade their GitLab instances to one of these versions to remediate the 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:>= 16.2.0, < 18.7.5>= 18.8.0, < 18.8.5= 18.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. Check GitLab version
    Run `sudo gitlab-rake gitlab:version` or check the GitLab admin panel under Help > Version. Alternatively, check the version file at /opt/gitlab/version or via the API endpoint /api/v4/version
    Affected if The installed version is >= 16.2.0 and < 18.7.5, OR >= 18.8.0 and < 18.8.5, OR equals 18.9.0
  2. Verify Mermaid diagram feature is enabled
    Navigate to GitLab admin area > Settings > Metrics and analytics, or check the gitlab.yml configuration file for mermaid/markdown diagram settings. Check if the feature flag 'mermaid_sandbox' or similar is enabled via the Rails console with `Feature.enabled?(:mermaid)`
    Affected if The Mermaid diagram rendering feature is enabled in the GitLab instance
  3. Check for unauthenticated access to Mermaid rendering
    Attempt to access a page containing a Mermaid diagram as an unauthenticated user, or review the GitLab application settings under General > Visibility and access controls to confirm anonymous/public access is permitted
    Affected if Unauthenticated or public users can view Markdown content that renders Mermaid diagrams

If the installed GitLab version falls within the affected ranges AND the Mermaid diagram feature is accessible to unauthenticated users, the environment is vulnerable to CVE-2026-0752.

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 18.7.5 / 18.8.5 or later
Fixed in 18.7.518.8.5
Interim mitigation

GitLab has released patched versions (18.7.5, 18.8.5, 18.9.1 and later). Organizations should upgrade their GitLab instances to one of these versions to remediate the vulnerability.

Recommended fix High confidence

Upgrade to GitLab 18.7.5 (or latest 18.7.x), 18.8.5 (or latest 18.8.x), or 18.9.1 (or latest stable 18.x) - recommend latest stable 18.x release

  1. 1. Identify the current GitLab installation version using `gitlab-rake gitlab:env:info` or the GitLab admin interface.
  2. 2. Based on your current version, determine the minimum upgrade target: if on 16.2.x to 18.6.x, upgrade to at least 18.7.5; if on 18.8.x, upgrade to at least 18.8.5; if on 18.9.0, upgrade to at least 18.9.1.
  3. 3. Review the GitLab upgrade documentation for your installation method (Omnibus or source): https://docs.gitlab.com/ee/update/
  4. 4. Before upgrading, backup your GitLab instance using `gitlab-rake gitlab:backup:create`.
  5. 5. For Omnibus installations, run `sudo apt-get update && sudo apt-get install gitlab-ce` (or `gitlab-ee` for Enterprise Edition).
  6. 6. For source installations, follow the upgrade path in the installation guide.
  7. 7. After upgrade, verify the version with `gitlab-rake gitlab:env:info` and confirm the Mermaid sandbox functionality works correctly.
Caveat Standard GitLab upgrade risks apply - review release notes for between-version breaking changes, especially when crossing major version boundaries

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

Fix this in GitLab Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
5.0 hours of engineering $890
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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