What happened
In GitLab CE/EE from 18.4 before 19.3.9, 19.4 before 19.4.8, and 19.5 before 19.5.6, an authenticated user holding an MCP-scoped OAuth token could, under certain conditions, perform unauthorized issuable state changes on issues/merge requests (CWE-639/CWE-863, CVSS 4.3). Fixed in the 19.5.6 patch release.
Why it matters
GitLab exposes an MCP server for AI agents to operate on issues/merge requests. A token scoped for MCP use granting broader issuable mutation than intended lets an agent (or a prompt-injected agent) change issue/MR state it should not be able to, which is a broken-access-control issue in the agent-authorization surface.
Attack vector
MCP-scoped OAuth token authorization scoping flaw lets an authenticated user perform issuable state changes without proper authorization
Affected systems
GitLab CE/EE 18.4 to <19.3.9, 19.4 to <19.4.8, 19.5 to <19.5.6
Mitigation
Upgrade to GitLab 19.3.9 / 19.4.8 / 19.5.6