CVE-2026-123142
GitLab MCP-scoped tokens could approve or merge beyond their intended scope
GitLab · GitLab GitLab MCP authorization
First documented disclosure · Review checkpoint
Summary
An MCP-limited OAuth token could perform unauthorized changes on issues or merge requests.
Severity and exploitation evidence
Medium · 4.3/10 · CVSS 3.1. Severity source.
Exploitation not established: Malicious exploitation status remains unverified in the reviewed sources.
Technical severity is not a measure of observed attacks or of risk to your deployment. Attempts, demonstrations, and successful compromise retain the qualifications in the source.
How the weakness works
Issuable state changes used incorrect token-scope authorization checks.
Conditions required
An authenticated user holds an MCP-scoped OAuth token.
Potential impact
Unauthorized issue changes, merge-request approvals or merges can occur.
Affected versions and configurations
18.4 through versions before 19.3.9, 19.4 before 19.4.8, and 19.5 before 19.5.6.
Fix and mitigation status
19.3.9, 19.4.8 and 19.5.6.
Practical next steps
Upgrade to a corrected release in the applicable maintenance branch.
Operating lesson
Check token scope at each repository mutation.
Evidence and limits
Original disclosure 2026-11-16. The CVE Program published this record 2026-11-17. CERT-FR’s November 17 GitLab bulletin also lists this identifier.
Sources
- GitLab CVE authority record
Primary source ·
- GitLab GitLab MCP authorization original advisory
Primary source ·
- CERT-FR GitLab advisory
Primary source ·
- ENISA EUVD-2026-126843
Primary source ·