dbcve.org
GitLabApplication

CVE-2025-8099

HIGH · 7.5 CVSS v3.1 Published 2026-02-11
Fix available
A fix is available. Upgrade to 18.6.6 / 18.7.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
GitLab has remediated an issue in GitLab CE/EE affecting all versions from 10.8 before 18.6.6, 18.7 before 18.7.4, and 18.8 before 18.8.4 that, under certain conditions, could have allowed an unauthenticated user to cause denial of service by sending repeated 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 unauthenticated attacker can send repeated GraphQL queries to GitLab CE/EE instances, potentially causing denial of service. The vulnerability exists in versions 10.8 through 18.6.5, 18.7.0-18.7.3, and 18.8.0-18.8.3.

MitigationUpgrade GitLab to version 18.6.6, 18.7.4, 18.8.4 or later. Alternatively, consider rate-limiting or temporarily blocking unauthenticated access to the GraphQL endpoint as a compensating control.

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:>= 10.8.0, < 18.6.6>= 18.7.0, < 18.7.4>= 18.8.0, < 18.8.4

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

CVSS:3.1/AV:N/AC:L/PR:N/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. Check installed GitLab version
    Run 'gitlab-rake gitlab:env:info' or check the admin dashboard under Help > Version. Alternatively, inspect the version file at /opt/gitlab/version or /usr/local/gitlab/version depending on installation method.
    Affected if The version falls within 10.8.0 to 18.6.5, 18.7.0 to 18.7.3, or 18.8.0 to 18.8.3 (i.e., < 18.6.6, < 18.7.4, or < 18.8.4). Compare your version to these ranges.
  2. Verify if GraphQL endpoint is accessible to unauthenticated users
    Attempt to access the /api/graphql endpoint without providing authentication credentials. Use a tool like curl: curl -s https://your-gitlab-instance/api/graphql -X POST -H 'Content-Type: application/json' -d '{"query":"{version}"}'
    Affected if The endpoint returns a valid GraphQL response instead of a 401 Unauthorized or 302 redirect to login, indicating unauthenticated access is possible.
  3. Confirm rate limiting is not applied to GraphQL
    Review GitLab's rate limiting settings in the Admin Area under Settings > Network > Rate Limiting. Check if specific rate limits are configured for the /api/graphql path or if the endpoint falls under default API limits.
    Affected if No rate limiting is configured for the GraphQL endpoint and the instance allows unauthenticated GraphQL access.
  4. Check if anonymous access is enabled in GraphQL settings
    Navigate to Admin Area > Settings > API or GraphQL settings. Look for settings controlling anonymous access to the GraphQL API.
    Affected if Anonymous or unauthenticated access to GraphQL is explicitly enabled.

You are affected if your GitLab version is less than 18.6.6, 18.7.4, or 18.8.4 AND the GraphQL endpoint at /api/graphql is accessible to unauthenticated users without rate limiting 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 18.6.6 / 18.7.4 / 18.8.4 or later
Fixed in 18.6.618.7.418.8.4
Interim mitigation

Upgrade GitLab to version 18.6.6, 18.7.4, 18.8.4 or later. Alternatively, consider rate-limiting or temporarily blocking unauthenticated access to the GraphQL endpoint as a compensating control.

Recommended fix High confidence

Upgrade to GitLab 18.6.6, 18.7.4, or 18.8.4 (or later) - recommended: 18.8.4 or latest stable 18.x release

  1. Identify your current GitLab version using `gitlab-rake gitlab:env:info` or checking the GitLab admin dashboard
  2. Determine which upgrade path applies based on your current version (10.8.0 to 18.6.x → upgrade to 18.6.6 or later; 18.7.x → upgrade to 18.7.4 or later; 18.8.x → upgrade to 18.8.4 or later)
  3. Back up your GitLab instance database and repository data before upgrading
  4. Follow the official GitLab upgrade documentation for your installation method (Omnibus, source, or Helm chart)
  5. For Omnibus installations: Run `sudo apt-get update && sudo apt-get install gitlab-ce` (or `gitlab-ee`) to upgrade to the desired version
  6. After upgrade, verify GitLab is running: `sudo gitlab-ctl status`
  7. Confirm the vulnerability is resolved by checking that repeated unauthenticated GraphQL queries no longer cause DoS conditions
Caveat Upgrading across many minor versions (e.g., from 10.x to 18.x) may have significant breaking changes; review the GitLab upgrade guides and release notes 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
  • Consultation2.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,290
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,664.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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