CVE-2026-1402: Allocation of Resources Without Limits or Throttling in GitLab
Published May 27, 2026
·Updated
GitLab has remediated an issue in GitLab CE/EE affecting all versions from 17.1 before 18.10.7, 18.11 before 18.11.4, and 19.0 before 19.0.1 that under certain conditions could have allowed an authenticated user to cause denial of service due to insufficient validation.
Affected Software
8 affected components
GitLab GitLab CE>=17.1<18.10.7, >=18.11<18.11.4, >=19.0<19.0.1
GitLab GitLab EE>=17.1<18.10.7, >=18.11<18.11.4, >=19.0<19.0.1
GitLab GitLab>=17.1.0<18.10.7
GitLab GitLab>=17.1.0<18.10.7
GitLab GitLab>=18.11.0<18.11.4
GitLab GitLab>=18.11.0<18.11.4
GitLab GitLab=19.0.0
GitLab GitLab=19.0.0
Remediation
Information
Upgrade to versions 18.10.7, 18.11.4, 19.0.1 or above.
Event History
May 27, 2026
CVE Published
via MITRE·05:55 PM
Data Sourced
via MITRE·05:55 PM
RemedyDescriptionSeverityWeakness
Data Sourced
via NVD·07:16 PM
DescriptionSeverityWeaknessAffected Software
Frequently Asked Questions
1
What is the severity of CVE-2026-1402?
CVE-2026-1402 has a medium severity score of 6.5.
2
How do I fix CVE-2026-1402?
To fix CVE-2026-1402, upgrade to GitLab versions 18.10.7, 18.11.4, 19.0.1 or above.
3
What software is affected by CVE-2026-1402?
CVE-2026-1402 affects GitLab CE and GitLab EE versions prior to 18.10.7, 18.11.4, and 19.0.1.
4
What kind of issue is described in CVE-2026-1402?
CVE-2026-1402 refers to an issue involving allocation of resources without limits that could lead to denial of service.
5
When was CVE-2026-1402 published?
CVE-2026-1402 was published on May 27, 2026.