Auth bypass in GitLab
CVE-2026-12664
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 read_api-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.
Vulnerability class: Broken Access Control
Published · last modified .
CVSS v3 metric
CVSS v3 base score 6.8 (Medium). Vector: CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N.
EPSS exploit prediction
No EPSS score from FIRST.org yet. New CVEs usually get one within a few days; no score means no signal yet, not low risk. How EPSS works.
Affected products
Weakness classification (CWE)
References
- gitlab.com/gitlab-org/gitlab/-/work_items/603510
- hackerone.com/reports/3735499 (technical-description, permissions-required, exploit)
- docs.gitlab.com/releases/patches/patch-release-gitlab-19-5-1-released/
Frequently asked questions
- What is CVE-2026-12664?
- CVE-2026-12664 is a medium-severity vulnerability in GitLab, classified under Incorrect Authorization. CVSS score: 6.8/10. Published 2026-10-22.
- How severe is CVE-2026-12664?
- Medium severity. CVSS v3 base score is 6.8 out of 10.