dbcve.org
GitLabApplication

CVE-2025-3922

MEDIUM · 6.5 CVSS v3.1 Published 2026-04-22
Fix available
A fix is available. Upgrade to 18.9.6 / 18.10.4 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 CE/EE affecting all versions from 12.4 before 18.9.6, 18.10 before 18.10.4, and 18.11 before 18.11.1 that could have allowed an authenticated user to cause denial of service by overwhelming system resources under certain conditions due to insufficient resource allocation limits in the GraphQL API.

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 by overwhelming system resources through the GraphQL API due to insufficient resource allocation limits. This affects GitLab CE/EE versions 12.4 through 18.9.5, 18.10.0-18.10.3, and 18.11.0.

MitigationUpgrade GitLab to version 18.9.6, 18.10.4, 18.11.1 or later to patch the insufficient resource allocation limits in the GraphQL API.

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:>= 12.4.0, < 18.9.6>= 18.10.0, < 18.10.4= 18.11.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. Determine installed GitLab version
    Run 'sudo gitlab-rake gitlab:env:info' or check the version file at '/opt/gitlab/version' or query the API with 'curl -s http://localhost/api/v4/version'
    Affected if The version number falls within 12.4.0 to 18.9.5, 18.10.0 to 18.10.3, or equals 18.11.0
  2. Confirm GraphQL API endpoint is accessible
    Verify the GraphQL endpoint responds at '/api/graphql' or '/api/v4/graphql' by sending a request to that URL
    Affected if The GraphQL API returns a valid response, indicating it is enabled and reachable
  3. Verify authentication is enabled for API access
    Check that user authentication is configured for the API, either through local user registration, LDAP/SSO integration, or OAuth. Confirm at least one authenticated user account exists in the system.
    Affected if Authenticated users can access the GraphQL API, which is the default configuration in GitLab

The environment is affected if the installed GitLab version is 12.4.0-18.9.5, 18.10.0-18.10.3, or 18.11.0 AND the GraphQL API is accessible to authenticated users, which is the default state.

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.9.6 / 18.10.4 or later
Fixed in 18.9.618.10.4
Interim mitigation

Upgrade GitLab to version 18.9.6, 18.10.4, 18.11.1 or later to patch the insufficient resource allocation limits in the GraphQL API.

Recommended fix High confidence

18.9.6, 18.10.4, or 18.11.1 (depending on your current version)

  1. 1. Back up your GitLab instance database and repositories before proceeding with the upgrade
  2. 2. Review the GitLab upgrade path documentation for your current version to ensure you follow a supported upgrade path
  3. 3. For versions >= 12.4.0 and < 18.9.6: upgrade to GitLab 18.9.6 or later
  4. 4. For versions >= 18.10.0 and < 18.10.4: upgrade to GitLab 18.10.4 or later
  5. 5. For version 18.11.0: upgrade to GitLab 18.11.1 or later
  6. 6. After upgrade, verify the GraphQL API is functioning correctly
  7. 7. Monitor system resources to confirm the DoS vulnerability is mitigated
Caveat Review GitLab release notes for your target version for any configuration or API changes that may affect your instance

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in GitLab Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,800
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,880.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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