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 CE/EE with MCP OAuth tokens
GitLab CE/EE incorrectly checks authorization for MCP-scoped OAuth tokens. An authenticated user who already holds such a token can, over the network and without further user interaction, change issue and merge-request state, including approving and merging, under certain conditions. Instances on the affected release lines are affected.
What to do: Upgrade GitLab CE/EE to 19.3.9, 19.4.8, or 19.5.6, matching the installed release line.
| Product | Affected | Fixed in |
|---|---|---|
| GitLab CE/EE | all versions from 18.4 before 19.3.9, 19.4 before 19.4.8, and 19.5 before 19.5.6 | 19.3.9, 19.4.8, and 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 CE/EE affecting all versions from 18.4 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 holding an MCP-scoped OAuth token to perform unauthorized issuable state changes on issues and merge requests, including approving and merging, 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