dbcve.org
GitLabApplication

CVE-2026-1184

HIGH · 7.5 CVSS v3.1 Published 2026-05-14
Fix available
A fix is available. Upgrade to 18.9.7 / 18.10.6 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 EE affecting all versions from 11.9 before 18.9.7, 18.10 before 18.10.6, and 18.11 before 18.11.3 that could have allowed an unauthenticated user to cause denial of service by uploading a specially crafted file due to improper validation.

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 EE versions 11.9 through 18.11.2 contain improper validation when handling file uploads, allowing unauthenticated users to upload specially crafted files that cause denial of service.

MitigationUpgrade GitLab to version 18.9.7, 18.10.6, 18.11.3 or later to remediate the improper validation vulnerability.

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:>= 11.9.0, < 18.9.7>= 18.10.0, < 18.10.6>= 18.11.0, < 18.11.3

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 installed GitLab version
    Run `gitlab-rake gitlab:env:info` or check /opt/gitlab/embedded/service/gitlab-rails/VERSION file. Alternatively, visit Admin Area > Settings > Metrics and profiling > Version on the web interface.
    Affected if The installed version falls within any of these ranges: 11.9.0 to 18.9.6, 18.10.0 to 18.10.5, or 18.11.0 to 18.11.2.
  2. Verify if unauthenticated project access is enabled
    Navigate to Admin Area > Settings > Visibility and access control, or check the gitlab.yml configuration file under the `default_projects_features` section. Look for whether guests or anonymous users have access to repositories or file download features.
    Affected if Anonymous or unauthenticated users are permitted read access to projects, which could allow them to trigger the file upload vulnerability.
  3. Confirm file upload/download features are accessible
    Check if the web interface allows file browsing or archive downloads without authentication. Test by attempting to download a project archive or browse repository files in a public project while logged out.
    Affected if Project archives, repository files, or other downloadable content is accessible to unauthenticated users.

The environment is affected if GitLab version is below 18.9.7, 18.10.6, or 18.11.3 AND the instance permits unauthenticated access to file download or repository features.

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.7 / 18.10.6 / 18.11.3 or later
Fixed in 18.9.718.10.618.11.3
Interim mitigation

Upgrade GitLab to version 18.9.7, 18.10.6, 18.11.3 or later to remediate the improper validation vulnerability.

Recommended fix High confidence

Upgrade to GitLab 18.9.7, 18.10.6, or 18.11.3 (or later). The recommended path is 18.11.3 as it includes all fixes.

  1. 1. Back up your GitLab instance database and configuration files before proceeding with the upgrade.
  2. 2. Stop GitLab services using: sudo gitlab-ctl stop
  3. 3. For Debian/Ubuntu systems, update the package repository and upgrade: sudo apt-get update && sudo apt-get install gitlab-ee (or use your package manager).
  4. 4. For RHEL/CentOS systems, run: sudo yum install gitlab-ee
  5. 5. Reconfigure GitLab: sudo gitlab-ctl reconfigure
  6. 6. Restart GitLab services: sudo gitlab-ctl start
  7. 7. Verify the upgrade by checking the version: sudo gitlab-rake gitlab:env:info
  8. 8. Ensure you are running version 18.9.7, 18.10.6, or 18.11.3 or later.
Caveat Review GitLab release notes for breaking changes between your current version and target version before upgrading, especially for major version jumps.

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

Fix this in GitLab Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing5.0 h
  • Review / QA3.0 h
17.0 hours of engineering $2,970
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,752.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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