dbcve.org
GitLabApplication

CVE-2025-10867

MEDIUM · 6.5 CVSS v3.1 Published 2025-09-26
Fix available
A fix is available. Upgrade to 18.2.7 / 18.3.3 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
An issue has been discovered in GitLab CE/EE affecting all versions from 18.1 before 18.2.7, 18.3 before 18.3.3, and 18.4 before 18.4.1 that could have allowed an authenticated user to create a denial-of-service condition by exploiting an unprotected GraphQL API through repeated requests.

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 but authenticated-user-only vulnerability exists in GitLab CE/EE versions 18.1 through 18.2.6, 18.3.0 through 18.3.2, and 18.4.0 where the GraphQL API endpoint lacks proper rate limiting or DoS protection, allowing authenticated users to send repeated requests that consume excessive server resources and cause denial-of-service conditions.

MitigationUpgrade GitLab to versions 18.2.7, 18.3.3, or 18.4.1 or later. Alternatively, implement upstream rate limiting on GraphQL endpoints as a compensating control until patching is possible.

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.1.0, < 18.2.7>= 18.3.0, < 18.3.3= 18.4.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
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. Check GitLab version
    Run `sudo gitlab-rake gitlab:version` or check the GitLab admin panel under Help > Version to obtain the exact installed version.
    Affected if The installed version is 18.1.0 through 18.2.6, 18.3.0 through 18.3.2, or exactly 18.4.0.
  2. Verify GraphQL endpoint is accessible
    Confirm the GraphQL endpoint is exposed by attempting to access `/-/graphql` or `/api/graphql` on the GitLab instance. This is a standard GitLab feature that is enabled by default.
    Affected if The GraphQL endpoint responds to requests, indicating it is enabled and accessible.
  3. Check for rate limiting configuration on GraphQL
    Review the GitLab configuration file (typically at `/etc/gitlab/gitlab.rb`) for rate limiting settings targeting the GraphQL API, such as `gitlab_rails['graphql_rate_limit']` or similar rate limit configurations. Also check the admin area under Settings > Network > Rate limits for GraphQL-specific limits.
    Affected if No rate limiting is configured specifically for GraphQL endpoints, or the configuration is missing entirely.
  4. Confirm authentication is not blocked
    Verify that the GraphQL endpoint accepts authenticated user requests. This is the default behavior in GitLab; ensure the instance does not have strict access controls that would prevent authenticated users from accessing the GraphQL API.
    Affected if Authenticated users can access and send repeated requests to the GraphQL endpoint without being blocked.

You are affected if your GitLab version falls within 18.1.0-18.2.6, 18.3.0-18.3.2, or 18.4.0 AND the GraphQL endpoint is accessible to authenticated users without rate limiting protections in place.

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.2.7 / 18.3.3 or later
Fixed in 18.2.718.3.3
Interim mitigation

Upgrade GitLab to versions 18.2.7, 18.3.3, or 18.4.1 or later. Alternatively, implement upstream rate limiting on GraphQL endpoints as a compensating control until patching is possible.

Recommended fix High confidence

Upgrade to GitLab 18.2.7, 18.3.3, or 18.4.1 (or later)

  1. 1. Back up your GitLab instance data and configuration before proceeding.
  2. 2. For GitLab installations using the official omnibus package, update your package repository and install the updated package.
  3. 3. For Docker installations, pull the new image tag (e.g., gitlab/gitlab-ee:18.2.7, gitlab/gitlab-ee:18.3.3, or gitlab/gitlab-ee:18.4.1) and recreate the container.
  4. 4. For source installations, clone the specific tag (e.g., v18.2.7, v18.3.3, or v18.4.1) and follow the standard upgrade procedure.
  5. 5. After upgrade, run 'gitlab-ctl reconfigure' to apply configuration changes.
  6. 6. Verify the upgrade by checking the GitLab version at /admin/about or via 'gitlab-rake gitlab:env:info'.

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
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
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,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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