Authenticated domain restriction bypass via crafted email
Published Apr 25, 2024 · Updated Nov 20, 2025
Authentication bypass in GitLab before 16.9.6 allows remote authenticated users to evade instance or group domain restrictions. GitLab validates a crafted email address as matching an allowed domain, but the restricted public references do not disclose the parsing or normalization error. Low-privileged network access and configured domain restrictions are required; the bypass permits access otherwise denied by policy.
Summary
What happened
Authentication bypass in GitLab before 16.9.6 allows remote authenticated users to evade instance or group domain restrictions. GitLab validates a crafted email address as matching an allowed domain, but the restricted public references do not disclose the parsing or normalization error. Low-privileged network access and configured domain restrictions are required; the bypass permits access otherwise denied by policy.
The record
- CVE
- CVE-2024-1347
- Published
- Apr 25, 2024
- Updated
- Nov 20, 2025
- Vendor
- GitLab
- Product
- GitLab
- Classifications
- CWE-290
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Apr 25, 2024CVE publishedPublication date reported by the CVE source.
- Nov 20, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0.0 <16.9.6
- Affected versionversion=16.10 <16.10.4
- Affected versionversion=16.11 <16.11.1
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo