dbcve.org
GitLabApplication

CVE-2026-1387

MEDIUM · 6.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 →
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 EE affecting all versions from 15.6 before 18.6.6, 18.7 before 18.7.4, and 18.8 before 18.8.4 that could have allowed an authenticated user to cause Denial of Service by uploading a malicious file and repeatedly querying it through GraphQl.

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 · moderate confidence

GitLab EE versions 15.6 prior to 18.6.6, 18.7 prior to 18.7.4, and 18.8 prior to 18.8.4 contain a Denial of Service vulnerability. An authenticated user can upload a specially crafted malicious file and repeatedly query it through GraphQL, causing the service to become unavailable.

MitigationUpgrade GitLab EE to version 18.6.6, 18.7.4, 18.8.4 or later. If immediate upgrade is not possible, consider restricting GraphQL API access or rate-limiting GraphQL queries as a temporary mitigation.

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:>= 15.6.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
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 installed GitLab EE version
    Run `gitlab-rake gitlab:version` or check the GitLab admin panel under /admin/application_settings or look at /opt/gitlab/version-manifest.txt
    Affected if The version is 15.6.0 to 18.6.5, 18.7.0 to 18.7.3, or 18.8.0 to 18.8.3 (these are the vulnerable ranges)
  2. Verify GraphQL API is accessible
    Attempt to access the GraphQL endpoint at /api/graphql (or /-/graphql) and confirm it returns a valid response rather than a 404
    Affected if GraphQL endpoint responds normally - the DoS requires GraphQL to be reachable
  3. Confirm file upload functionality is enabled
    Check if users can upload attachments or files through the GitLab web interface, API, or via merge request attachments
    Affected if File uploads are permitted - the attack requires uploading a malicious file that will be queried
  4. Look for signs of DoS activity
    Monitor GraphQL query response times and error rates; check if the GraphQL service is unresponsive or timing out on repeated file queries
    Affected if GraphQL queries to specific uploaded files cause service slowdown or unavailability

A user is affected if their GitLab EE version falls within the vulnerable ranges AND GraphQL API is accessible AND file uploads are enabled, as the attack requires both conditions to trigger the DoS.

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 EE to version 18.6.6, 18.7.4, 18.8.4 or later. If immediate upgrade is not possible, consider restricting GraphQL API access or rate-limiting GraphQL queries as a temporary mitigation.

Recommended fix High confidence

Upgrade to GitLab 18.6.6 (if on 18.6.x), 18.7.4 (if on 18.7.x), or 18.8.4 (if on 18.8.x)

  1. 1. Identify the current GitLab version by navigating to the GitLab admin area or running `sudo gitlab-rake gitlab:env:info`
  2. 2. Determine which version branch you are on (15.6.x-18.5.x, 18.6.x, 18.7.x, or 18.8.x) to select the appropriate upgrade target
  3. 3. Create a full backup of the GitLab instance using `sudo gitlab-backup-create`
  4. 4. Stop GitLab services with `sudo gitlab-ctl stop`
  5. 5. Update the GitLab package repository and install the fixed version: For 18.6.x branch upgrade to 18.6.6; for 18.7.x branch upgrade to 18.7.4; for 18.8.x branch upgrade to 18.8.4 (e.g., `sudo apt-get update && sudo apt-get install gitlab-ee=18.6.6-ee.0` or equivalent for your package manager)
  6. 6. Reconfigure GitLab with `sudo gitlab-ctl reconfigure`
  7. 7. Restart GitLab services with `sudo gitlab-ctl start`
  8. 8. Verify the upgrade was successful by checking the version at Admin Area > Dashboard or running `sudo gitlab-rake gitlab:env:info`
Caveat GitLab minor/patch upgrades typically have low risk but review the release notes for any known issues or migration requirements specific to your version branch

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
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,840
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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