GitLabApplication
CVE-2025-12664
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 · uneditedGitLab has remediated an issue in GitLab CE/EE affecting all versions from 13.0 before 18.8.9, 18.9 before 18.9.5, and 18.10 before 18.10.3 that could have allowed an unauthenticated user to cause denial of service by sending repeated GraphQL queries.
In the news
Third-party coverageSurfaced from public web coverage — external links open in a new tab.
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 confidenceGitLab CE/EE versions 13.0 through 18.8.8, 18.9.0-18.9.4, and 18.10.0-18.10.2 contain a denial of service vulnerability where unauthenticated users can send repeated GraphQL queries to exhaust server resources and cause service unavailability.
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
>= 13.0.0, < 18.8.9>= 18.9.0, < 18.9.5>= 18.10.0, < 18.10.3CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Determine GitLab versionAccess the GitLab admin dashboard or run `gitlab-rake gitlab:env:info` to retrieve the installed GitLab version numberAffected if The displayed version falls within these ranges: >= 13.0.0 and < 18.8.9, OR >= 18.9.0 and < 18.9.5, OR >= 18.10.0 and < 18.10.3
-
Confirm GraphQL endpoint is accessibleAttempt to access the GraphQL endpoint at your GitLab instance URL with a path such as /api/graphql or /graphql (a successful response indicates the endpoint is exposed)Affected if The GraphQL endpoint returns a response, indicating it is enabled and reachable
-
Check if rate limiting is configured for GraphQLReview the GitLab configuration files (gitlab.rb or gitlab.yml) for any rate_limit settings specifically applied to the GraphQL endpoint; also check the Admin Area > Settings > Network > Rate limiting for GraphQL-related rulesAffected if No rate limiting rules are defined or enabled specifically for the GraphQL endpoint, leaving it unprotected against repeated requests
A user is affected if their GitLab version is in the vulnerable range AND the GraphQL endpoint is accessible AND no rate limiting is configured for that endpoint.
Generated from the published advisory. Verify against your own configuration.
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 · scoped18.8.918.9.518.10.3
Upgrade GitLab to version 18.8.9, 18.9.5, or 18.10.3 or later to patch the vulnerability.
18.8.9, 18.9.5, or 18.10.3 (or any later version)
- Back up your GitLab instance data and configuration before proceeding with any upgrade
- Review GitLab's official upgrade documentation for your installation method (omnibus, source, etc.)
- Plan your upgrade path based on your current version: if on 13.x through 18.8.x, upgrade to 18.8.9; if on 18.9.x, upgrade to 18.9.5; if on 18.10.x, upgrade to 18.10.3
- Execute the upgrade following GitLab's standard upgrade procedure for your deployment method
- After upgrade, verify GitLab services are running correctly and test GraphQL endpoint functionality
- Confirm the version number matches the expected fixed release
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
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 locallyCheck whether your project pulls in CVE-2025-12664 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-12664 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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