GPU VulnDB

Database/Control plane, storage & DevOps

GitLab: MCP-scoped OAuth token can approve and merge merge requests beyond its scope

CVSS 4.3CVE-2026-123142Control plane, storage & DevOpscurated

Impact

An authorization check is wrong for OAuth tokens scoped to GitLab's MCP interface. A token holder can change the state of issues and merge requests, including approving and merging them, even though the token's scope should not allow it. MCP tokens are the ones handed to AI agents and LLM tooling, so a leaked or prompt-injected agent token can push changes into the repositories that hold infrastructure code, cluster manifests and GitOps sources. Affects 18.4 before 19.3.9, 19.4 before 19.4.8 and 19.5 before 19.5.6.

Who can reach it

An authenticated user, or an agent, holding an MCP-scoped OAuth token on a project. Network access to the GitLab instance is required.

What to do

Upgrade to 19.3.9, 19.4.8 or 19.5.6 per the GitLab 19.5.6 patch release. On a self-managed instance this is a package upgrade and a service restart (Omnibus reconfigure/restart or a Helm chart bump), with no effect on GPU nodes beyond a short GitLab outage. Afterwards, review merges and approvals made with MCP-scoped tokens during the affected window, and revoke agent tokens that are not needed.

References

Related entries

All Control plane, storage & DevOps entries

This entry is curated: imported from vendor advisories with machine assistance, not yet individually verified. Confirm against your vendor's advisory before acting, and report anything wrong.