dbcve.org
GitLabApplication

CVE-2026-1724

HIGH · 7.5 CVSS v3.1 Published 2026-03-25
Fix available
A fix is available. Upgrade to 18.8.7 / 18.9.3 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
GitLab has remediated an issue in GitLab EE affecting all versions from 18.5 before 18.8.7, 18.9 before 18.9.3, and 18.10 before 18.10.1 that could have allowed an unauthenticated user to access API tokens of self-hosted AI models due to improper access control.

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 improper access control vulnerability in GitLab EE that allowed unauthenticated users to access API tokens configured for self-hosted AI models. The issue stemmed from insufficient access controls on AI model configuration endpoints, enabling exposure of sensitive authentication credentials without authentication.

MitigationUpgrade GitLab EE to version 18.8.7, 18.9.3, 18.10.1 or later as specified in the official GitLab security advisory. Review and rotate any potentially exposed AI model API tokens as a precautionary measure.

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:>= 18.5.0, < 18.8.7>= 18.9.0, < 18.9.3= 18.10.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
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. Confirm GitLab edition is Enterprise Edition
    Run `sudo gitlab-rake gitlab:env:info` or check the UI at /help for the edition designation. This vulnerability affects only GitLab EE, not CE.
    Affected if The instance is running GitLab Community Edition (CE) rather than Enterprise Edition (EE)
  2. Identify installed GitLab version
    Run `sudo gitlab-rake gitlab:git:version` or check the /help page in the GitLab UI. Compare the version number to the affected ranges: 18.5.0 through 18.8.6, 18.9.0 through 18.9.2, or exactly 18.10.0.
    Affected if The installed version falls within >= 18.5.0 and < 18.8.7, or >= 18.9.0 and < 18.9.3, or equals 18.10.0
  3. Determine if AI model integrations are configured
    Navigate to the AI model configuration settings in the GitLab admin UI (Admin Area > Model Registry > AI Gateway) or check for configured AI providers in the gitlab.rb/gitlab.yml configuration files.
    Affected if Self-hosted AI models or AI gateway endpoints are configured with API tokens or authentication credentials
  4. Verify API token exposure via unauthenticated endpoint access
    Attempt to access the AI model configuration API endpoint without authentication (e.g., GET /api/v4/ai_models, /api/v4/ai_settings, or similar endpoints) using an unauthenticated request via curl or a browser.
    Affected if The endpoint returns sensitive AI model API tokens or credentials without requiring authentication

A user is affected if running GitLab EE at a version within the affected ranges AND has self-hosted AI models configured with API tokens, AND those configuration endpoints are accessible without authentication.

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.8.7 / 18.9.3 or later
Fixed in 18.8.718.9.3
Interim mitigation

Upgrade GitLab EE to version 18.8.7, 18.9.3, 18.10.1 or later as specified in the official GitLab security advisory. Review and rotate any potentially exposed AI model API tokens as a precautionary measure.

Recommended fix High confidence

18.8.7, 18.9.3, 18.10.1, or latest stable 18.x release (whichever corresponds to your current branch)

  1. 1. Identify the current GitLab version by running `sudo gitlab-rake gitlab:env:info` or checking the GitLab admin area
  2. 2. Create a full backup of the GitLab instance using `sudo gitlab-backup-create`
  3. 3. For GitLab versions >= 18.5.0 and < 18.8.7: Upgrade to version 18.8.7 or the latest 18.8.x stable release
  4. 4. For GitLab versions >= 18.9.0 and < 18.9.3: Upgrade to version 18.9.3 or the latest 18.9.x stable release
  5. 5. For GitLab version 18.10.0: Upgrade to version 18.10.1 or the latest 18.10.x stable release
  6. 6. After upgrade, verify the GitLab instance is operational and test that AI model integrations work correctly
  7. 7. Review audit logs to confirm no unauthorized access occurred prior to the upgrade
Caveat Standard GitLab upgrade caveats apply - review release notes for any configuration changes required; ensure compatibility with your CI/CD pipelines and integrations

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

Fix this in GitLab Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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