CVE-2026-1500: Allocation of Resources Without Limits or Throttling in GitLab
GitLab has remediated an issue in GitLab CE/EE affecting all versions from 17.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 authenticated user to cause denial of service due to uncontrolled resource consumption when processing a specially crafted file upload.
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-1500?
The severity of CVE-2026-1500 is medium, with a CVSS score of 6.5.
How do I fix CVE-2026-1500?
To fix CVE-2026-1500, upgrade to GitLab versions 18.10.8, 18.11.5, or 19.0.2 and above.
What does CVE-2026-1500 affect?
CVE-2026-1500 affects GitLab CE and GitLab EE versions from 17.10 before 18.10.8, 18.11 before 18.11.5, and 19.0 before 19.0.2.
What is the risk associated with CVE-2026-1500?
CVE-2026-1500 has a risk score of 38, indicating potential denial of service due to uncontrolled resource consumption.
Who is impacted by CVE-2026-1500?
Authenticated users in GitLab could potentially exploit CVE-2026-1500 to cause denial of service.