# CVE-2026-12664: GitLab CE/EE improper access control in GraphQL work item email field

Source: https://junglewise.ai/threats/cve-2026-12664-gitlab-has-remediated-an-issue-in-gitlab-ce-ee-affecting-all  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-10-22. Updated: 2026-10-22  
License: CC BY 4.0 with a link back

CVE-2026-12664 · Severity: medium · CVSS 6.8 · Published 2026-10-22

GitLab is a platform for managing software development projects and repositories. An authenticated user with limited API permissions could bypass those restrictions to retrieve sensitive project email addresses and create work items, potentially gaining unauthorized access to project communications. This affects self-managed GitLab installations across multiple recent versions.

Technologies: [GitLab EE](https://junglewise.ai/threats/technologies/ee), [GitLab CE](https://junglewise.ai/threats/technologies/gitlab-ce). Vendors: [GitLab](https://junglewise.ai/threats/vendors/gitlab).

## Quick answers

**Is CVE-2026-12664 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-12664 being exploited in the wild.

**How severe is CVE-2026-12664?** Medium severity, with a CVSS score of 6.8, published 22 October 2026.

**Which products and versions are affected?** GitLab EE 18.2 before 19.3.6, 19.4 before 19.4.3, 19.5 before 19.5.1; GitLab CE 18.2 before 19.3.6, 19.4 before 19.4.3, 19.5 before 19.5.1.

**Is there a fix for CVE-2026-12664?** Yes: fixed in GitLab CE/EE 19.3.6, 19.4.3, 19.5.1. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**How is CVE-2026-12664 attacked?** It is attacked over the network, in a web application.

**Am I affected by CVE-2026-12664?** Check whether you run GitLab EE or GitLab CE at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## How to fix

- Fixed in GitLab CE/EE 19.3.6, 19.4.3, 19.5.1

## Technical details

An improper access control vulnerability in a GraphQL field allows an authenticated user with read_api-scoped tokens to retrieve incoming email addresses and create work items beyond their token's intended scope. The issue stems from insufficient scope enforcement on the affected GraphQL field. Authentication is required but the attacker only needs a low-privilege read_api token.

## Affected products

- GitLab CE 18.2 before 19.3.6, 19.4 before 19.4.3, 19.5 before 19.5.1
- GitLab EE 18.2 before 19.3.6, 19.4 before 19.4.3, 19.5 before 19.5.1

## Timeline

- 2026-10-21: disclosed
- 2026-10-21: patched

## References

- [https://docs.gitlab.com/releases/patches/patch-release-gitlab-19-5-1-released/](https://docs.gitlab.com/releases/patches/patch-release-gitlab-19-5-1-released/)
- [https://gitlab.com/gitlab-org/gitlab/-/work_items/603510](https://gitlab.com/gitlab-org/gitlab/-/work_items/603510)

## Related threats

- [GitLab authorization bypass in group milestones API](https://junglewise.ai/threats/cve-2026-13319-gitlab-has-remediated-an-issue-in-gitlab-ce-ee-affecting-all)
- [GitLab integer overflow in regular expression compiler](https://junglewise.ai/threats/cve-2026-110264-an-issue-has-been-discovered-in-gitlab-ce-ee-affecting-all)
- [GitLab CE/EE integer overflow in CI/CD regular expression compiler](https://junglewise.ai/threats/cve-2026-97229-gitlab-has-remediated-an-issue-in-gitlab-ce-ee-affecting-all)
- [GitLab open redirect in Kubernetes proxy](https://junglewise.ai/threats/cve-2026-7767-gitlab-has-remediated-an-issue-in-gitlab-ce-ee-affecting-all)
- [GitLab incorrect authorization in fine-grained personal access tokens](https://junglewise.ai/threats/cve-2026-78335-gitlab-has-remediated-an-issue-in-gitlab-ce-ee-affecting-all)