dbcve.org
GitLabApplication

CVE-2025-1278

HIGH · 7.5 CVSS v3.1 Published 2025-05-09
Fix available
A fix is available. Upgrade to 17.9.8 / 17.10.6 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 CE/EE affecting all versions from 12.0 before 17.9.8, 17.10 before 17.10.6, and 17.11 before 17.11.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 CE/EE contains an authentication bypass vulnerability where under certain conditions users can circumvent administrator-configured IP access restrictions, allowing unauthorized access to sensitive information. The vulnerability affects versions 12.0 through 17.9.7, 17.10.0-17.10.5, and 17.11.0-17.11.1.

MitigationUpgrade GitLab to version 17.9.8, 17.10.6, or 17.11.2 or later. Review access logs for unauthorized access attempts from IPs outside allowed ranges.

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.9.8>= 17.10.0, < 17.10.6>= 17.11.0, < 17.11.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 'gitlab-rake gitlab:env:info' or view the version in the Admin Area > Dashboard. Compare the version to the affected ranges: < 17.9.8, 17.10.0-17.10.5, or 17.11.0-17.11.1
    Affected if The installed version falls within 12.0.0 to 17.9.7, 17.10.0 to 17.10.5, or 17.11.0 to 17.11.1
  2. Verify IP access restrictions are configured
    Navigate to Admin Area > Settings > Network > IP Restrictions, or check for 'ip_restrictions' entries in the GitLab database table 'application_settings'. The vulnerability only applies if IP restrictions are enabled.
    Affected if IP access restrictions are enabled on the GitLab instance
  3. Review access logs for unauthorized IP access
    Examine GitLab production logs (typically in /var/log/gitlab/gitlab-rails/production_json.log) or the 'audit_events' table for API calls or user sessions originating from IP addresses not in the configured allowlist
    Affected if Audit logs show access from IPs outside the configured IP restriction range that succeeded when it should have been blocked

You are affected if GitLab is running a version between 12.0.0 and 17.9.7, 17.10.0-17.10.5, or 17.11.0-17.11.1 AND IP access restrictions are configured.

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.9.8 / 17.10.6 / 17.11.2 or later
Fixed in 17.9.817.10.617.11.2
Interim mitigation

Upgrade GitLab to version 17.9.8, 17.10.6, or 17.11.2 or later. Review access logs for unauthorized access attempts from IPs outside allowed ranges.

Recommended fix High confidence

17.9.8 (or later in 17.9.x), 17.10.6 (or later in 17.10.x), or 17.11.2 (or later in 17.11.x) - recommend latest stable in your current minor branch

  1. Identify your current GitLab version using `sudo gitlab-rake gitlab:env:info`
  2. Determine which version branch you are currently running (17.9.x, 17.10.x, or 17.11.x)
  3. Back up your GitLab data and configuration using `sudo gitlab-backup-create`
  4. Update your GitLab installation to the appropriate fixed version: For 17.9.x line: upgrade to 17.9.8 or later; For 17.10.x line: upgrade to 17.10.6 or later; For 17.11.x line: upgrade to 17.11.2 or later
  5. Run `sudo gitlab-ctl reconfigure` after upgrade to apply configuration changes
  6. Verify the upgrade was successful and GitLab is running: `sudo gitlab-rake gitlab:check`
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
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,690
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,304.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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