dbcve.org
GitLabApplication

CVE-2026-6713

MEDIUM · 5.3 CVSS v3.1 Published 2026-05-27
Fix available
A fix is available. Upgrade to 18.10.7 / 18.11.4 or later.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

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 18.2 before 18.10.7, 18.11 before 18.11.4, and 19.0 before 19.0.1 that under certain conditions could have allowed an unauthorized user to enumerate private projects due to incorrect authorization checks.

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

GitLab CE/EE versions 18.2 prior to 18.10.7, 18.11 prior to 18.11.4, and 19.0 prior to 19.0.1 contain an authorization flaw where incorrect permission checks under certain conditions allow unauthenticated or unauthorized users to enumerate private project names and metadata that should be concealed.

MitigationUpgrade GitLab to version 18.10.7 or later for 18.x branches, 18.11.4 or later for 18.11 branch, or 19.0.1 or later for 19.0 branch. The vulnerability has been remediated in these patched releases.

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:>= 18.2.0, < 18.10.7>= 18.11.0, < 18.11.4= 19.0.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
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/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 installed GitLab version
    Run `sudo gitlab-rake gitlab:env:info` or check /opt/gitlab/version-manifest.txt to retrieve the exact version number
    Affected if Version falls within 18.2.0 to <18.10.7, 18.11.0 to <18.11.4, or equals 19.0.0
  2. Verify if private projects exist
    As an admin, run `sudo gitlab-rake gitlab:git:fsck` or check the GitLab UI under Projects > Your Projects to see if any projects have visibility set to Private
    Affected if The instance contains private projects and the GitLab version is in the affected range
  3. Test unauthenticated project enumeration
    Attempt to access private project endpoints via API without authentication: `curl -s https://gitlab-instance/api/v4/projects` or try to enumerate project IDs to see if private project names/metadata are returned
    Affected if Private project names or metadata are returned to unauthenticated users when they should not be visible

If the GitLab version is in the affected range (18.2.x, 18.11.x, or 19.0.0) and private projects exist, the environment may be vulnerable to unauthorized project enumeration.

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.10.7 / 18.11.4 or later
Fixed in 18.10.718.11.4
Interim mitigation

Upgrade GitLab to version 18.10.7 or later for 18.x branches, 18.11.4 or later for 18.11 branch, or 19.0.1 or later for 19.0 branch. The vulnerability has been remediated in these patched releases.

Recommended fix High confidence

Upgrade to GitLab 18.10.7, 18.11.4, or 19.0.1 (or later versions within your release branch)

  1. Backup your GitLab instance data before proceeding with any upgrade
  2. Identify your current GitLab version by running `gitlab-rake gitlab:env:info` or checking the GitLab admin area
  3. If running GitLab 18.2.0 through 18.10.6, upgrade to GitLab 18.10.7 or later
  4. If running GitLab 18.11.0 through 18.11.3, upgrade to GitLab 18.11.4 or later
  5. If running GitLab 19.0.0, upgrade to GitLab 19.0.1 or later
  6. For Omnibus installations, update using `apt-get update && apt-get install gitlab-ce` (or `gitlab-ee` for Enterprise Edition)
  7. For source installations, follow the upgrade instructions in GitLab documentation for your specific version
  8. After upgrade, verify the GitLab version with `gitlab-rake gitlab:env:info`
Caveat Review GitLab release notes for any breaking changes between your current version and target version before upgrading

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 / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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