Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB
CVE-2025-0679 Overview
CVE-2025-0679 is an information disclosure vulnerability in GitLab Community Edition (CE) and Enterprise Edition (EE). The flaw allows unauthorized users to view full email addresses that the application should display in a partially obscured format. The issue affects all GitLab versions from 17.1 before 17.10.7, 17.11 before 17.11.3, and 18.0 before 18.0.1. The weakness is categorized under [CWE-359] (Exposure of Private Personal Information to an Unauthorized Actor). GitLab addressed the issue in patch releases across the affected branches.
Critical Impact
Low-privileged network attackers can harvest full email addresses that GitLab intentionally masked, enabling targeted phishing and account enumeration against GitLab users.
Affected Products
- GitLab Community Edition versions 17.1 through 17.10.6
- GitLab Community/Enterprise Edition versions 17.11 through 17.11.2
- GitLab Community/Enterprise Edition version 18.0.0
Discovery Timeline
- 2025-05-22 - CVE-2025-0679 published to the National Vulnerability Database
- 2026-06-17 - Last updated in NVD database
Technical Details for CVE-2025-0679
Vulnerability Analysis
The vulnerability resides in GitLab's handling of user email visibility. GitLab normally obscures portions of email addresses when rendering them to users who should not see the full identifier. Under specific conditions, that masking logic is bypassed and the API or UI returns the complete, unredacted email string. The flaw requires authenticated but low-privileged access, mapping to a Privileges Required: Low vector. The impact is limited to confidentiality of personal information, with no integrity or availability consequences.
Email disclosure in a developer platform like GitLab has outsized practical value. Attackers who collect full addresses can correlate them with public commits, build targeted phishing campaigns against maintainers, or feed credential-stuffing workflows against corporate single sign-on portals. For additional context, review the GitLab Issue #514751 and the HackerOne Report #2952536.
Root Cause
The root cause is incomplete enforcement of email privacy controls in one or more GitLab endpoints. The server-side obfuscation routine responsible for returning masked addresses is not applied uniformly across every code path that renders user data. When a vulnerable path is reached, the raw email value from the user record is serialized directly into the response.
Attack Vector
An attacker needs a valid, low-privileged GitLab account on the target instance. The attacker then issues normal application requests to the affected endpoints and reads the full email address from responses that should have been masked. No user interaction, elevated role, or specialized tooling is required. Public GitLab.com and self-hosted instances running the affected versions are both exposed.
No verified public exploit code is available. See the HackerOne Report #2952536 for the researcher's technical write-up.
Detection Methods for CVE-2025-0679
Indicators of Compromise
- Authenticated API requests to GitLab endpoints that return user objects, especially from accounts that enumerate large numbers of user IDs or project memberships in a short window.
- Response payloads containing fully formed email addresses for users who configured email privacy settings.
- Unusual spikes in traffic from low-privileged tokens against user listing, project member, and comment-related endpoints.
Detection Strategies
- Review GitLab production_json.log and API audit events for high-volume user lookups originating from a single session or personal access token.
- Compare the email values returned by API responses against expected masked formats to identify leakage before patching.
- Correlate GitLab access logs with downstream phishing reports targeting GitLab contributors.
Monitoring Recommendations
- Alert on personal access tokens that iterate sequentially through user or project IDs.
- Baseline normal API call volume per authenticated user and flag deviations.
- Forward GitLab audit and application logs to a centralized analytics platform for retention and correlation.
How to Mitigate CVE-2025-0679
Immediate Actions Required
- Upgrade self-managed GitLab instances to version 17.10.7, 17.11.3, or 18.0.1 or later as applicable to your release branch.
- Rotate personal access tokens and session cookies for accounts suspected of harvesting user data.
- Audit recent API usage for signs of mass email enumeration prior to applying the patch.
Patch Information
GitLab released fixed versions 17.10.7, 17.11.3, and 18.0.1. GitLab.com has already been updated. Self-managed administrators should follow standard GitLab upgrade procedures and validate the installed version with gitlab-rake gitlab:env:info after the upgrade.
Workarounds
- Restrict account creation on internet-facing GitLab instances to trusted users to reduce the pool of low-privileged attackers.
- Enforce administrator approval for new sign-ups until the patch is deployed.
- Rate-limit authenticated API traffic to slow enumeration attempts against user and member endpoints.
# Verify installed GitLab version after upgrade
sudo gitlab-rake gitlab:env:info | grep "GitLab information" -A 5
# Example: require administrator approval for new sign-ups (gitlab.rb)
# gitlab_rails['gitlab_signup_enabled'] = false
# gitlab_rails['gitlab_require_admin_approval_after_user_signup'] = true
sudo gitlab-ctl reconfigure
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB

