GitLab CE/EE EUVD-2026-107680

Requires the attacker to already possess a valid authenticated token with the read_api scope (PR:L); it is not exploitable by anonymous or unauthenticated users. Exploitation targets a specific GraphQL field whose scope enforcement is insufficient, and the description qualifies it as occurring only 'under certain conditions' (reflected as AC:H), implying it is not a universal, every-request trigger. Impact is bounded to disclosing a project's incoming email address and creating work items within the token holder's reachable projects, rather than arbitrary data access. Limiting factors: valid read_api token prerequisite, conditional trigger path, and the narrow functional scope of the leaked/abused data.

This is a moderate-priority authorization flaw (CWE-863, improper scope enforcement) rather than a critical emergency. The provided CVSS of 6.8 (CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N) is network-reachable but gated by two meaningful brakes: PR:L means the attacker must already hold a valid, authenticated read_api-scoped token, and AC:H reflects that exploitation only works 'under certain conditions.' No EPSS score, KEV listing, or SSVC decision data was supplied, so automatability and exploitation-maturity signals cannot be weighed. Publicly available exploit code exists (a HackerOne report, #3735499), which raises likelihood somewhat, but POC availability is NOT the same as active exploitation and there is no evidence this is being exploited in the wild. The most important caveat is a signal conflict: the input's C:H/I:H impact rating appears inflated for the described outcome - leaking a project's incoming email address and creating work items - which is a limited information-disclosure and limited-integrity issue, not full confidentiality/integrity compromise; this materially lowers real-world severity below what 6.8 suggests. Net assessment: a genuine access-control bug worth patching on a normal cycle, but not a drop-everything issue given the required authenticated token, conditional trigger, and constrained impact.

An authenticated GitLab user (or a compromised/leaked read_api-scoped personal access token intended only for read operations) queries a specific GraphQL field that fails to enforce the token's scope. Through this, the attacker reads the target project's confidential incoming email address and creates work items despite holding only read permissions. Public exploit code referenced on HackerOne lowers the effort needed to reproduce the request.