CVE-2026-12664
Incorrect Authorization in GitLab
Reported by gitlab · Published October 21, 2026
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.
Fixed versions
Upgrade to a fixed version or later. Language registries are listed first, then Linux distributions, then vendor products.
| Package | Ecosystem | Fixed in |
|---|---|---|
| GitLab | GitLab | 19.5.1, 19.4.3, 19.3.6 |
Risk scores
Affected products
| Vendor | Product | Versions |
|---|---|---|
| GitLab | GitLab | 18.2, 19.4, 19.5 |
| GitLab | GitLab | 18.2, 19.4, 19.5 |
Timeline
- Oct 21, 2026 CVE Published
- Oct 22, 2026 EPSS Score (4 in total, the first dated here)
- Oct 23, 2026 CVE Updated
Query this with the API
The same record, from the CLI:
vulnetix vdb vuln CVE-2026-12664
vulnetix vdb fixes CVE-2026-12664Or with curl, using the org id and key from your account page:
curl -s -H "Authorization: ApiKey ${VULNETIX_ORG_ID}:${VULNETIX_API_KEY}" \
"https://api.vdb.vulnetix.com/v2/vuln/CVE-2026-12664/fixes/registry"The Community plan is free and allows 50 queries a day. Get a free API key · API quickstart
References
- HackerOne Bug Bounty Report #3735499 technical-descriptionexploitpermissions-required