CVE-2026-12664: Incorrect Authorization in GitLab
GitLab has remediated an issue in GitLab CE/EE affecting all versions from 18.2 before 19.3.6, 19.4 before 19.4.3, and 19.5 before 19.5.1 that, under certain conditions, could have allowed an authenticated user with a readapi-scoped token to retrieve a project's incoming email address and create work items, bypassing the token's restrictions, due to insufficient scope enforcement on a GraphQL field.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
GitLab CE/EEto a version that resolves this vulnerability.Fixed in 19.3.6 - Upgrade
Upgrade
GitLab CE/EEto a version that resolves this vulnerability.Fixed in 19.4.3 - Upgrade
Upgrade
GitLab CE/EEto a version that resolves this vulnerability.Fixed in 19.5.1
Event History
Frequently Asked Questions
Which deployments are affected?
GitLab CE/EE is affected in all versions from 18.2 before 19.3.6, 19.4 before 19.4.3, and 19.5 before 19.5.1.
What access does an attacker need?
An attacker needs to be authenticated and possess a token scoped to read_api. Exploitation also depends on the unspecified conditions under which the affected GraphQL field can be used.
What could an attacker do with successful exploitation?
They could retrieve a project's incoming email address and create work items despite the read_api token's intended restrictions.
How can the issue be remediated?
Upgrade to GitLab 19.3.6, 19.4.3, or 19.5.1, as appropriate for the release line in use.