CVE-2026-7250: Allocation of Resources Without Limits or Throttling in GitLab
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.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
GitLab CE/EEto a version that resolves this vulnerability.Fixed in 18.10.8 - Upgrade
Upgrade
GitLab CE/EEto a version that resolves this vulnerability.Fixed in 18.11.5 - Upgrade
Upgrade
GitLab CE/EEto a version that resolves this vulnerability.Fixed in 19.0.2
Event History
Frequently Asked Questions
What is the severity of CVE-2026-7250?
The severity of CVE-2026-7250 is rated high with a CVSS score of 7.5.
How do I fix CVE-2026-7250?
To fix CVE-2026-7250, upgrade GitLab to versions 18.10.8, 18.11.5, or 19.0.2 and above.
What software is affected by CVE-2026-7250?
CVE-2026-7250 affects all versions of GitLab CE/EE from 12.10 before 18.10.8, 18.11 before 18.11.5, and 19.0 before 19.0.2.
What type of vulnerability is CVE-2026-7250?
CVE-2026-7250 is classified as an allocation of resources without limits or throttling, specifically relating to improper input validation.
What impact can CVE-2026-7250 have?
CVE-2026-7250 could allow an unauthenticated user to cause a denial of service due to improper input validation in the API.