dbcve.org
GitLabApplication

CVE-2025-5069

MEDIUM · 6.5 CVSS v3.1 Published 2025-09-26
Fix available
A fix is available. Upgrade to 18.2.7 / 18.3.3 or later.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable 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
An issue has been discovered in GitLab CE/EE affecting all versions from 17.10 before 18.2.7, 18.3 before 18.3.3, and 18.4 before 18.4.1 that could have allowed an authenticated user to gain unauthorized access to confidential issues by creating a project with an identical name to the victim's project.

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

This is an authorization bypass vulnerability in GitLab where an authenticated user can create a project with the same name as an existing project they don't have access to, allowing them to gain unauthorized access to confidential issues in the victim's project. The issue stems from insufficient validation during project creation that may cause name collision or incorrect access control resolution.

MitigationUpgrade GitLab to version 18.2.7, 18.3.3, or 18.4.1 or later. Review existing projects for any unauthorized access or name collisions that may have occurred.

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:>= 17.10.0, < 18.2.7>= 18.3.0, < 18.3.3= 18.4.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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/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 your GitLab version
    Run 'gitlab-rake gitlab:env:info' or check the version file at /opt/gitlab/embedded/service/gitlab-rails/VERSION
    Affected if The installed version falls within >= 17.10.0 and < 18.2.7, OR >= 18.3.0 and < 18.3.3, OR equals 18.4.0
  2. Identify projects with duplicate names
    Query the database: SELECT namespace_id, name, COUNT(*) as cnt FROM projects GROUP BY namespace_id, name HAVING COUNT(*) > 1; or use the GitLab API to list all projects and check for name collisions within the same namespace
    Affected if Multiple projects share the same name within a single namespace, indicating a potential name collision exploit
  3. Review project access controls
    Use the API endpoint GET /projects/:id/members/all to compare authorized users against expected access lists, or run: gitlab-rake gitlab:git:fsck to check repository integrity
    Affected if Users are listed as members on projects they should not have access to, or unexpected users appear in project member lists
  4. Audit issue access for confidential projects
    Query the database: SELECT p.name as project, i.title, i.confidential, u.username FROM issues i JOIN projects p ON i.project_id = p.id JOIN users u ON i.author_id = u.id WHERE i.confidential = true; then compare against project membership
    Affected if Users without proper authorization can view or list confidential issues in projects outside their normal access scope

You are affected if your GitLab version is within the vulnerable range AND you detect project name collisions or unauthorized user access to confidential issues.

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.2.7 / 18.3.3 or later
Fixed in 18.2.718.3.3
Interim mitigation

Upgrade GitLab to version 18.2.7, 18.3.3, or 18.4.1 or later. Review existing projects for any unauthorized access or name collisions that may have occurred.

Recommended fix High confidence

Upgrade to GitLab 18.4.1 or later (or 18.2.7 for 17.x branches, 18.3.3 for 18.3 branches)

  1. 1. Back up your GitLab instance database and configuration before upgrading.
  2. 2. For GitLab installations using omnibus packages: Run 'sudo apt-get update && sudo apt-get install gitlab-ce' (or gitlab-ee for Enterprise Edition).
  3. 3. For installations using source: Follow the upgrade documentation for your specific version path.
  4. 4. After upgrade, verify that the GitLab version is >= 18.4.1 (or appropriate fixed version for your branch).
  5. 5. Review project access controls to ensure confidential issues have appropriate visibility settings.
  6. 6. Monitor for any unauthorized access attempts that may have occurred before the fix.
Caveat Standard GitLab upgrade considerations apply - review release notes for deprecations; minor version upgrades typically have low breaking change risk

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-2025-5069 — 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-5069 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