dbcve.org
GitLabApplication

CVE-2025-9958

HIGH · 7.7 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 →
83/100
Remediation priority · High
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 14.10 before 18.2.7, 18.3 before 18.3.3, and 18.4 before 18.4.1, that could have allowed Guest users to access sensitive information stored in virtual registry configurations.

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

GitLab CE/EE versions 14.10 through 18.4 before specified patches contained an improper access control vulnerability where Guest users could access sensitive information stored in virtual registry configurations. This allowed low-privilege users to view configuration data that should have been restricted to higher-privileged roles.

MitigationUpgrade GitLab to version 18.2.7, 18.3.3, 18.4.1 or later to remediate the vulnerability. Alternatively, review and restrict Guest user permissions to registry configurations until patching can be completed.

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:>= 14.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
Changed
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/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. Identify installed GitLab version
    Run `sudo gitlab-rake gitlab:version` or check the GitLab admin dashboard under Help > Version to obtain the exact version number
    Affected if The installed version falls within >= 14.10.0 and < 18.2.7, OR >= 18.3.0 and < 18.3.3, OR equals 18.4.0
  2. Verify if Container Registry is enabled
    Check if the GitLab Container Registry feature is active by navigating to the admin area under Settings > Registry, or query the GitLab API endpoint `/api/v4/settings` and look for the `registry_enabled` parameter
    Affected if Registry is enabled and the GitLab version is within the affected ranges
  3. Confirm virtual registry configuration exists
    Examine if any projects have virtual registry settings configured. This can be done via the GitLab API using `GET /api/v4/registries` with administrator credentials, or by reviewing project settings in the UI under Packages & Registries > Container Registry
    Affected if Virtual registry configurations exist and the GitLab version is vulnerable
  4. Test Guest user access to registry information
    Create or use a test account with Guest role and attempt to access registry configuration data via the GitLab API (`GET /api/v4/registries`) or through the web interface under registry-related pages
    Affected if A Guest user can successfully retrieve registry configuration details that should only be visible to higher-privileged users such as Developers or Maintainers

You are affected if your GitLab version is 14.10.0 through 18.2.6, 18.3.0 through 18.3.2, or 18.4.0, and the Container Registry feature is enabled with virtual registry configurations accessible to Guest users.

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, 18.4.1 or later to remediate the vulnerability. Alternatively, review and restrict Guest user permissions to registry configurations until patching can be completed.

Recommended fix High confidence

18.2.7, 18.3.3, or 18.4.1 (or later stable releases)

  1. 1. Backup your GitLab instance database and repositories before proceeding with any upgrade
  2. 2. Determine your current GitLab version by running: sudo gitlab-rake gitlab:env:info
  3. 3. Plan your upgrade path based on your current version - if below 18.2.7, upgrade to 18.2.7 or later; if at 18.3.0-18.3.2, upgrade to 18.3.3 or later; if at 18.4.0, upgrade to 18.4.1 or later
  4. 4. For GitLab installations using Omnibus: sudo apt-get update && sudo apt-get install gitlab-ce (or gitlab-ee) to install the latest available fixed version
  5. 5. For source installations: follow the upgrade documentation at https://docs.gitlab.com/ee/update/ to rebuild from the fixed release
  6. 6. After upgrade, run sudo gitlab-rake gitlab:check to verify the installation
  7. 7. Confirm the fix by verifying that Guest users can no longer access virtual registry configurations
Caveat GitLab upgrades may require database migrations - review release notes for any required manual steps and ensure compatibility with your underlying infrastructure before upgrading

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

Fix this in GitLab Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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