dbcve.org
GitLabApplication

CVE-2025-5982

HIGH · 7.5 CVSS v3.1 Published 2025-06-12
Fix available
A fix is available. Upgrade to 17.10.8 / 17.11.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 issue has been discovered in GitLab EE affecting all versions from 12.0 before 17.10.8, 17.11 before 17.11.4, and 18.0 before 18.0.2. Under certain conditions users could bypass IP access restrictions and view sensitive information.

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 EE contains an authorization bypass vulnerability where under certain conditions, users can circumvent IP access restrictions (allowlists) configured at the project, group, or instance level to view sensitive information they should not have access to.

MitigationUpgrade GitLab EE to version 17.10.8, 17.11.4, or 18.0.2 or later. Until patched, review IP access restriction configurations and consider implementing additional authentication controls such as two-factor authentication.

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:>= 12.0.0, < 17.10.8>= 17.11.0, < 17.11.4>= 18.0.0, < 18.0.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. Determine installed GitLab version
    Run command: sudo gitlab-rake gitlab:env:info 2>/dev/null || cat /opt/gitlab/version 2>/dev/null || check the Admin Area > Settings > General page
    Affected if Version is 12.0.0 to 17.10.7, 17.11.0 to 17.11.3, or 18.0.0 to 18.0.1
  2. Verify IP access restrictions exist at project level
    Navigate to Project > Settings > Repository > Protected branches or Project > Settings > CI/CD > General pipelines, or query the API: GET /projects/:id or inspect project settings JSON export
    Affected if Any IP allowlist or IP restriction rule is defined for project-level access controls
  3. Verify IP access restrictions exist at group level
    Navigate to Group > Settings > Permissions > CI/CD tokens or Group > Settings > Webhooks, or query the API: GET /groups/:id
    Affected if Any IP allowlist is configured restricting group-level access to the GitLab instance or its resources
  4. Verify IP access restrictions exist at instance level
    Check Admin Area > Settings > Network > Outbound requests, or Admin Area > Settings > Pages, or query the API: GET /application/settings
    Affected if Any instance-level IP allowlist or IP restriction is enabled in GitLab settings

You are affected if your GitLab version falls within the affected ranges AND you have IP access restrictions (allowlists) configured at any level (project, group, or instance).

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.10.8 / 17.11.4 / 18.0.2 or later
Fixed in 17.10.817.11.418.0.2
Interim mitigation

Upgrade GitLab EE to version 17.10.8, 17.11.4, or 18.0.2 or later. Until patched, review IP access restriction configurations and consider implementing additional authentication controls such as two-factor authentication.

Recommended fix High confidence

Upgrade to 17.10.8, 17.11.4, or 18.0.2 or later (recommended: latest stable 17.x or 18.x release)

  1. 1. Backup your GitLab instance and database before proceeding with any upgrade
  2. 2. Review the GitLab upgrade path documentation for your current version to ensure you follow a supported upgrade path
  3. 3. For GitLab installations using the official Omnibus packages: run 'sudo apt-get update && sudo apt-get install gitlab-ee' (Debian/Ubuntu) or 'sudo yum install gitlab-ee' (RHEL/CentOS)
  4. 4. For GitLab installations using source: clone the specific tag (e.g., v17.10.8) and follow the upgrade from source documentation
  5. 5. After upgrade, verify the IP access restrictions are functioning correctly by testing from allowed and blocked IP addresses
  6. 6. Monitor GitLab logs for any unauthorized access attempts
Caveat Major version upgrades (e.g., 12.x to 17.x) may require database migrations and could have breaking changes - review the Changelog for each intermediate version

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
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
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,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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