dbcve.org
GitLabApplication

CVE-2025-10004

HIGH · 7.5 CVSS v3.1 Published 2025-10-09
Fix available
A fix is available. Upgrade to 18.2.8 / 18.3.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 13.12 to 18.2.8, 18.3 to 18.3.4, and 18.4 to 18.4.2 that could make the GitLab instance unresponsive or severely degraded by sending crafted GraphQL queries requesting large repository blobs.

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 contains a denial-of-service vulnerability where crafted GraphQL queries requesting large repository blobs can exhaust server resources, making the instance unresponsive or severely degraded.

MitigationUpgrade to GitLab versions 18.2.9, 18.3.5, 18.4.3 or later. If immediate upgrade is not possible, consider rate-limiting or temporarily disabling GraphQL API access.

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:>= 13.12.0, < 18.2.8>= 18.3.0, < 18.3.4>= 18.4.0, < 18.4.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
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. Identify GitLab version
    Run `sudo gitlab-rake gitlab:version` or check the GitLab admin panel under the Help section to find the exact installed version number
    Affected if The version falls within these ranges: >= 13.12.0 and < 18.2.8, OR >= 18.3.0 and < 18.3.4, OR >= 18.4.0 and < 18.4.2
  2. Confirm GraphQL API is accessible
    Verify the GraphQL endpoint responds at `/api/graphql` by making a test request or checking that the feature is not disabled in gitlab.rb/gitlab.yml under `graphql` settings
    Affected if GraphQL endpoint is enabled and reachable - this is required for the vulnerability to be exploitable
  3. Review GraphQL query logs for anomalies
    Check GitLab production logs (`/var/log/gitlab/gitlab-rails/production.log`) or the audit logs for repeated large blob requests through the GraphQL API, looking for patterns of resource-intensive queries
    Affected if Logs show frequent or bulk GraphQL queries requesting large repository blobs that correlate with high CPU or memory usage on the GitLab server

You are affected if your GitLab version is in the vulnerable ranges AND the GraphQL API is accessible, particularly if server performance degrades when GraphQL queries request large blobs.

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.8 / 18.3.4 / 18.4.2 or later
Fixed in 18.2.818.3.418.4.2
Interim mitigation

Upgrade to GitLab versions 18.2.9, 18.3.5, 18.4.3 or later. If immediate upgrade is not possible, consider rate-limiting or temporarily disabling GraphQL API access.

Recommended fix High confidence

18.2.8, 18.3.4, 18.4.2, or latest stable 18.x release

  1. 1. Back up your GitLab instance database and repositories before upgrading
  2. 2. Identify your current GitLab version in Admin Area > Settings > Metrics and profiling > Version
  3. 3. For GitLab 13.12.x through 18.2.x: upgrade to version 18.2.8 or later (recommended: latest 18.2.x stable)
  4. 4. For GitLab 18.3.x: upgrade to version 18.3.4 or later (recommended: latest 18.3.x stable)
  5. 5. For GitLab 18.4.x: upgrade to version 18.4.2 or later (recommended: latest 18.4.x stable)
  6. 6. Use the official GitLab upgrade instructions for your installation method (omnibus, source, or Helm chart)
  7. 7. After upgrade, verify the GraphQL endpoint is accessible and the instance responds normally
  8. 8. Test with a simple GraphQL query to confirm normal operation
Caveat Standard GitLab minor version upgrade risks apply; review GitLab release notes for deprecations and breaking changes in your target version

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
  • Testing6.0 h
  • Review / QA3.0 h
19.0 hours of engineering $3,320
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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