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.
Authorization flaw leaks secrets in GitLab EE Duo Agent
GitLab EE's Duo Agent Platform did not properly authorize secret detection findings. An authenticated user who already had access to those findings could, under certain conditions, view unredacted secret values over the network without further interaction. GitLab EE from 19.1 before 19.3.9, 19.4 before 19.4.8, and 19.5 before 19.5.6 is affected.
What to do: Upgrade GitLab EE to 19.3.9, 19.4.8, or 19.5.6, matching the installed 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, 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 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 view unredacted secret values from secret detection findings they had access to through GitLab Duo Agent Platform due to improper 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