GitLab patches 37 flaws in 19.5.6, 19.4.8 and 19.3.9
Four issues are high severity, including stored XSS and a CI/CD race that can expose protected variables.
Incorrect authorization in GitLab EE pipeline policies
GitLab Enterprise Edition mishandles authorization for scheduled pipeline execution policies after they are unassigned. An authenticated user, under certain conditions and with user interaction, can run code in protected pipelines. Versions from 19.1 before 19.3.9, 19.4 before 19.4.8, and 19.5 before 19.5.6 are affected.
What to do: Upgrade GitLab EE to 19.3.9, 19.4.8, or 19.5.6 on the matching release line.
| Product | Affected | Fixed in |
|---|---|---|
| GitLab EE | 19.1 before 19.3.9, 19.4 before 19.4.8, and 19.5 before 19.5.6 | 19.3.9, 19.4.8, 19.5.6 |
Order-of-magnitude estimate by the model from install counts, market share and public scan data it knows; verify before quoting.
GitLab has remediated an issue in GitLab EE affecting all versions from 19.1 before 19.3.9, 19.4 before 19.4.8, and 19.5 before 19.5.6 that under certain conditions could have allowed an authenticated user to run code in protected pipelines through a scheduled pipeline execution policy after the policy had been unassigned due to incorrect authorization checks.
Four issues are high severity, including stored XSS and a CI/CD race that can expose protected variables.
Today 1.1K readers · 1.3K views · 176 reads · all time 202K views