dbcve.org
GitLabApplication

CVE-2025-1042

HIGH · 7.5 CVSS v3.1 Published 2025-02-12
Fix available
A fix is available. Upgrade to 17.6.5 / 17.7.4 or later.
See remediation →
84/100
Remediation priority · High
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
An insecure direct object reference vulnerability in GitLab EE affecting all versions from 15.7 prior to 17.6.5, 17.7 prior to 17.7.4, and 17.8 prior to 17.8.2 allows an attacker to view repositories in an unauthorized way.

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

An Insecure Direct Object Reference (IDOR) vulnerability in GitLab EE allows authenticated or potentially unauthenticated attackers to access repository references without proper authorization, enabling unauthorized viewing of repositories they should not have access to.

MitigationUpgrade GitLab EE to version 17.6.5, 17.7.4, 17.8.2 or later to patch the IDOR vulnerability in repository access controls.

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.7.0, < 17.6.5>= 17.7.0, < 17.7.4>= 17.8.0, < 17.8.2

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
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/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 installed GitLab version
    Run `sudo gitlab-rake gitlab:version` or check the GitLab admin panel under Help > Version to determine the exact version number
    Affected if The installed version falls within any of these ranges: >= 15.7.0 and < 17.6.5, OR >= 17.7.0 and < 17.7.4, OR >= 17.8.0 and < 17.8.2
  2. Verify repository access controls are in use
    Review GitLab project settings at Project > Settings > Repository > Protected branches and review whether any public or internal projects exist that reference private repositories
    Affected if Public or internal projects exist that contain references to private repository paths that should not be accessible to all users
  3. Check external user authentication settings
    Navigate to Admin Area > Settings > General > Sign-up restrictions and verify whether external users are permitted or anonymous access is enabled
    Affected if External users are enabled or the instance allows unauthenticated (public) access to any repository content
  4. Review audit logs for unauthorized repository reference access
    In GitLab Admin Area > Monitoring > Audit Events, search for events involving repository_refs or project access patterns, particularly from users without explicit project membership
    Affected if Audit logs show repository reference access attempts by users who are not members of the target projects

If the installed GitLab version is within the affected ranges AND the instance exposes any public/internal projects or allows external/unauthenticated users, the IDOR vulnerability could allow unauthorized repository reference access.

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.6.5 / 17.7.4 / 17.8.2 or later
Fixed in 17.6.517.7.417.8.2
Interim mitigation

Upgrade GitLab EE to version 17.6.5, 17.7.4, 17.8.2 or later to patch the IDOR vulnerability in repository access controls.

Recommended fix High confidence

Upgrade to 17.6.5, 17.7.4, or 17.8.2 (or later stable releases) depending on your current major version

  1. 1. Back up your GitLab instance including database, repositories, and configuration files
  2. 2. Update your GitLab package repository to get the latest packages
  3. 3. Stop GitLab services (gitlab-ctl stop)
  4. 4. Install the updated package using your package manager (e.g., apt-get install gitlab-ee or yum install gitlab-ee)
  5. 5. Run gitlab-ctl reconfigure to apply configuration changes
  6. 6. Start GitLab services (gitlab-ctl start)
  7. 7. Verify the upgrade was successful by checking GitLab version and accessing the instance
Caveat Review GitLab release notes for 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-2025-1042 — 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-1042 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