EUVD-2025-209367
GHSA-m3c6-4xg4-583x
Severity by source
AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N
Primary rating from NVD · only source for this CVE.
CVSS VectorNVD
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N
Lifecycle Timeline
4DescriptionCVE.org
GitLab has remediated an issue in GitLab EE affecting all versions from 16.6 before 18.8.9, 18.9 before 18.9.5, and 18.10 before 18.10.3 that under certain circumstances could have allowed an authenticated user to have access to other users' email addresses via certain GraphQL queries.
AnalysisAI
Authenticated users in GitLab EE versions 16.6-18.8.8, 18.9-18.9.4, and 18.10-18.10.2 can expose other users' email addresses through specific GraphQL queries due to improper authorization checks. An authenticated attacker can enumerate valid user accounts and retrieve their email addresses without additional privileges, violating confidentiality. No public exploit code or active exploitation has been confirmed; patches are available in GitLab 18.8.9, 18.9.5, and 18.10.3.
Technical ContextAI
The vulnerability stems from insufficient authorization validation (CWE-862: Missing Authorization) in GitLab's GraphQL API endpoint. GitLab EE implements role-based access control for user data exposure, but certain GraphQL query constructs bypass these checks, allowing an authenticated user to traverse the schema and retrieve email attributes meant to be restricted. The root cause is a logic flaw in GraphQL field resolver authorization rather than a cryptographic or injection vulnerability. This affects only GitLab EE (Enterprise Edition); Community Edition is unaffected per vendor statement.
RemediationAI
Upgrade GitLab EE to patched versions: 18.8.9 or later, 18.9.5 or later, or 18.10.3 or later, depending on your current deployment track. If immediate patching is not feasible, restrict GraphQL API access via firewall or reverse-proxy rules to limit authenticated query execution, or disable public GraphQL query introspection. Audit GraphQL query logs for anomalous user-enumeration patterns and review user access to sensitive data endpoints. Refer to the official GitLab security advisory (https://about.gitlab.com/releases/2026/04/08/patch-release-gitlab-18-10-3-released/) and the issue tracker (https://gitlab.com/gitlab-org/gitlab/-/issues/565363) for full remediation guidance.
An issue has been discovered in GitLab CE/EE affecting all versions from 16.1 prior to 16.1.6, 16.2 prior to 16.2.9, 16.
The SSH key upload feature (lib/gitlab_keys.rb) in gitlab-shell before 1.7.3, as used in GitLab 5.0 before 5.4.1 and 6.x
An issue has been discovered in GitLab CE/EE affecting all versions starting from 11.9. Rated critical severity (CVSS 10
A vulnerability in GitLab CE/EE affecting all versions from 11.10 prior to 15.1.6, 15.2 to 15.2.4, 15.3 to 15.3.2 allows
The Kubernetes integration in GitLab Enterprise Edition 11.x before 11.2.8, 11.3.x before 11.3.9, and 11.4.x before 11.4
The Ruby SAML library is for implementing the client side of a SAML authorization. Rated critical severity (CVSS 9.8), t
A hardcoded password was set for accounts registered using an OmniAuth provider (e.g. Rated critical severity (CVSS 9.8)
An issue has been discovered in GitLab CE/EE affecting all versions starting from 12.10 before 14.6.5, all versions star
When requests to the internal network for webhooks are enabled, a server-side request forgery vulnerability in GitLab af
An issue has been discovered in GitLab CE/EE affecting all versions starting from 13.7.9 before 13.8.7, all versions sta
An issue was discovered in GitLab Omnibus 7.4 through 12.2.1. Rated critical severity (CVSS 9.8), this vulnerability is
An issue was discovered in GitLab Community and Enterprise Edition 9.x, 10.x, and 11.x before 11.5.8, 11.6.x before 11.6
Same weakness CWE-862 – Missing Authorization
View allSame technique Authentication Bypass
View allShare
External POC / Exploit Code
Leaving vuln.today