dbcve.org
GitLabApplication

CVE-2026-7250

HIGH · 7.5 CVSS v3.1 Published 2026-06-11
Fix available
A fix is available. Upgrade to 18.10.8 / 18.11.5 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 12.10 before 18.10.8, 18.11 before 18.11.5, and 19.0 before 19.0.2 that under certain conditions could have allowed an unauthenticated user to cause denial of service due to improper input validation in the API request parsing middleware.

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

An improper input validation vulnerability in GitLab's API request parsing middleware allows unauthenticated attackers to trigger denial of service by sending specially crafted API requests. The vulnerability affects multiple GitLab versions from 12.10 through 19.0 and is exploitable without any authentication.

MitigationUpgrade GitLab to version 18.10.8, 18.11.5, or 19.0.2 or later. For production deployments, schedule maintenance window and ensure backups exist before performing the upgrade.

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.10.0, < 18.10.8>= 18.11.0, < 18.11.5>= 19.0.0, < 19.0.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. Check installed GitLab version
    Run `gitlab-rake gitlab:env:info` or check the version file at /opt/gitlab/version for omnibus installations. In GitLab UI, navigate to Admin area > Overview > Dashboard to view the version.
    Affected if Version falls within >= 12.10.0, < 18.10.8 OR >= 18.11.0, < 18.11.5 OR >= 19.0.0, < 19.0.2
  2. Confirm API is exposed
    Verify that the GitLab API endpoint is accessible. This is typically at /api/v4/ on the GitLab instance. Check if the instance accepts HTTP/HTTPS requests to the API path.
    Affected if API endpoint is reachable from network without authentication - no specific feature enablement required, the vulnerability exists in the API parsing middleware by default

The environment is affected if the installed GitLab version matches any of the three vulnerable ranges (12.10.0-18.10.7, 18.11.0-18.11.4, or 19.0.0-19.0.1) and the API is network-accessible, since exploitation requires no authentication.

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.10.8 / 18.11.5 / 19.0.2 or later
Fixed in 18.10.818.11.519.0.2
Interim mitigation

Upgrade GitLab to version 18.10.8, 18.11.5, or 19.0.2 or later. For production deployments, schedule maintenance window and ensure backups exist before performing the upgrade.

Recommended fix High confidence

18.10.8, 18.11.5, or 19.0.2 (depending on current version branch)

  1. 1. Identify the current installed GitLab version by running `gitlab-rake gitlab:env:info` or checking the GitLab admin area
  2. 2. Determine the appropriate target version based on current version: if on 12.10.x-18.9.x upgrade to 18.10.8; if on 18.11.x upgrade to 18.11.5; if on 19.0.x-19.0.1 upgrade to 19.0.2
  3. 3. Back up the GitLab database and repository data before upgrading
  4. 4. For self-managed installations, update the package repository and upgrade using: `sudo apt-get update` followed by `sudo apt-get install gitlab-ce` (or `gitlab-ee`)
  5. 5. Alternatively, for Docker installations: stop the container, pull the new image tag, and recreate the container with the new image
  6. 6. Run `sudo gitlab-ctl reconfigure` after package installation to apply configuration
  7. 7. Verify the upgrade was successful by checking the GitLab version at Admin Area > Settings > General or via `gitlab-rake gitlab:env:info`
  8. 8. Confirm the vulnerability is remediated by ensuring the version shown is 18.10.8, 18.11.5, 19.0.2 or later
Caveat Major version upgrades (e.g., 17.x to 18.x) may include breaking changes; review GitLab release notes before upgrading across major versions

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

Fix this in GitLab Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
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,120.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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