Database/Control plane, storage & DevOps

GitLab CE/EE: GraphQL field ignores read_api token scope, allowing writes and email-address disclosure

CVSS 6.8CVE-2026-12664Control plane, storage & DevOpscurated

Impact

A GraphQL field did not enforce token scope, so an authenticated user holding only a read_api-scoped token could read a project's incoming email address and create work items. The read-only guarantee of a scoped token is what lets operators hand automation and third-party integrations limited access to the CI/CD system that drives the fleet; this breaks that boundary and turns a read token into a write primitive, plus leaks an address that accepts inbound project mail. The impact is confined to GitLab itself - no code execution and no direct reach into GPU nodes - but it undermines how access to the pipeline platform is delegated. Affected: all versions from 18.2 before 19.3.6, 19.4 before 19.4.3, 19.5 before 19.5.1.

Who can reach it

An authenticated GitLab user with a read_api-scoped token, over the network. The advisory notes the conditions required are specific and the scored vector rates attack complexity high.

What to do

Upgrade self-managed GitLab to 19.5.1, 19.4.3, or 19.3.6 and restart the services - the standard patch cycle for a single host or deployment, no GPU-node impact. Same patch release as CVE-2026-105777, so bundle them into one maintenance window.

References

https://nvd.nist.gov/vuln/detail/CVE-2026-12664 https://docs.gitlab.com/releases/patches/patch-release-gitlab-19-5-1-released/https://gitlab.com/gitlab-org/gitlab/-/work_items/603510 https://hackerone.com/reports/3735499

This entry is curated: imported from vendor advisories with machine assistance, not yet individually verified. Confirm against your vendor's advisory before acting, and report anything wrong.