dbcve.org
GitLabApplication

CVE-2026-1101

MEDIUM · 6.5 CVSS v3.1 Published 2026-04-08
Fix available
A fix is available. Upgrade to 18.8.9 / 18.9.5 or later.
See remediation →
71/100
Remediation priority · Elevated
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
GitLab has remediated an issue in GitLab EE affecting all versions from 18.2 before 18.8.9, 18.9 before 18.9.5, and 18.10 before 18.10.3 that could have allowed an authenticated user to cause denial of service to the GitLab instance due to improper input validation in GraphQL queries.

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 authenticated user can cause denial of service to GitLab EE instances due to improper input validation in GraphQL queries. This affects versions 18.2 through 18.8.8, 18.9.0-18.9.4, and 18.10.0-18.10.2. The vulnerability allows specially crafted GraphQL queries to trigger excessive resource consumption.

MitigationUpgrade GitLab to version 18.8.9, 18.9.5, 18.10.3 or later. These versions contain the proper input validation fix for the GraphQL query handler.

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.2, < 18.8.9>= 18.9.0, < 18.9.5>= 18.10.0, < 18.10.3

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

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

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 GitLab installation and edition
    Run 'sudo gitlab-rake gitlab:env:info' or check /opt/gitlab/version to confirm GitLab Enterprise Edition is installed
    Affected if The installed product is GitLab Enterprise Edition (not Community Edition)
  2. Determine installed GitLab version
    Run 'sudo gitlab-rake gitlab:env:info' or check /var/opt/gitlab/gitlab-rails/VERSION to retrieve the exact version number
    Affected if The version falls within these ranges: >= 18.2 and < 18.8.9; OR >= 18.9.0 and < 18.9.5; OR >= 18.10.0 and < 18.10.3
  3. Verify GraphQL API is accessible
    Confirm the GraphQL endpoint is reachable at /api/graphql (e.g., curl -s -o /dev/null -w '%{http_code}' https://your-gitlab-instance/api/graphql)
    Affected if GraphQL API returns HTTP 200 and accepts queries (the vulnerability only applies when GraphQL is enabled and reachable)
  4. Confirm user authentication is enabled
    Check if internal user registration or external authentication (e.g., LDAP, SAML, OAuth) is configured in /etc/gitlab/gitlab.rb under 'gitlab_rails["gitlab_signin"]' or via the Admin Area > Settings
    Affected if Authenticated users can access the GitLab instance (the vulnerability requires an authenticated user to send malicious GraphQL queries)

You are affected if you run GitLab Enterprise Edition with a version in the affected ranges AND the GraphQL API is accessible to authenticated 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.8.9 / 18.9.5 / 18.10.3 or later
Fixed in 18.8.918.9.518.10.3
Interim mitigation

Upgrade GitLab to version 18.8.9, 18.9.5, 18.10.3 or later. These versions contain the proper input validation fix for the GraphQL query handler.

Recommended fix High confidence

Upgrade to 18.8.9, 18.9.5, or 18.10.3 (whichever is the next minor release in your current version branch)

  1. 1. Back up your GitLab instance data and database before proceeding with the upgrade.
  2. 2. Identify your current GitLab version to determine the appropriate upgrade target.
  3. 3. For GitLab versions >= 18.2 and < 18.8.9: upgrade to version 18.8.9 or later.
  4. 4. For GitLab versions >= 18.9.0 and < 18.9.5: upgrade to version 18.9.5 or later.
  5. 5. For GitLab versions >= 18.10.0 and < 18.10.3: upgrade to version 18.10.3 or later.
  6. 6. Follow GitLab's official upgrade documentation for your deployment method (omnibus, source, or Helm chart).
  7. 7. After upgrade, verify the GitLab instance is running and accessible.
  8. 8. Test GraphQL API functionality to confirm the fix is working properly.
Caveat Review GitLab release notes for your target version for any breaking changes or required migration steps

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
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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