GitLab: Authentication Bypass via Malicious CI Triggers

Summary

GitLab has fixed a bug in certain versions of its software that could have allowed an authenticated user to crash the system. This could happen if the user had the right permissions and exploited a weakness in the way the system handled certain API requests. To stay safe, update to the latest version of GitLab.

What to do

No fix is available yet. Check with your software vendor for updates.

Affected software

Vendor	Product	Affected versions	Fix available
gitlab	gitlab	> 9.0.0 , <= 18.7.5	–
gitlab	gitlab	> 9.0.0 , <= 18.7.5	–
gitlab	gitlab	> 18.8.0 , <= 18.8.5	–
gitlab	gitlab	> 18.8.0 , <= 18.8.5	–
gitlab	gitlab	18.9.0	–
gitlab	gitlab	18.9.0	–

Original title

GitLab has remediated an issue in GitLab CE/EE affecting all versions from 9.0 before 18.7.5, 18.8 before 18.8.5, and 18.9 before 18.9.1 that could have, under certain circumstances, allowed an aut...

Original description

GitLab has remediated an issue in GitLab CE/EE affecting all versions from 9.0 before 18.7.5, 18.8 before 18.8.5, and 18.9 before 18.9.1 that could have, under certain circumstances, allowed an authenticated user with certain access to cause Denial of Service by creating specially crafted CI triggers via the API.

nvd CVSS3.1 6.5

Vulnerability type

CWE-770 Allocation of Resources Without Limits

https://about.gitlab.com/releases/2026/02/25/patch-release-gitlab-18-9-1-release... Release Notes Vendor Advisory
https://gitlab.com/gitlab-org/gitlab/-/issues/535662 Broken Link
https://hackerone.com/reports/3045257 Permissions Required