Repository access via skipped SSO enforcement
Published Sep 29, 2023 · Updated Nov 20, 2025
Authorization bypass in GitLab EE allows remote authenticated users to access public members-only repositories without enforced SSO. The SSO access check treats users granted project membership directly or through an invited group as eligible without requiring an identity-provider session. The target must enforce SAML SSO on a public project whose repository is limited to members, and the account must hold direct or shared-group membership.
Summary
What happened
Authorization bypass in GitLab EE allows remote authenticated users to access public members-only repositories without enforced SSO. The SSO access check treats users granted project membership directly or through an invited group as eligible without requiring an identity-provider session. The target must enforce SAML SSO on a public project whose repository is limited to members, and the account must hold direct or shared-group membership.
The record
- CVE
- CVE-2023-3115
- Published
- Sep 29, 2023
- Updated
- Nov 20, 2025
- Vendor
- GitLab
- Product
- GitLab
- Classifications
- CWE-286, T1190
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Sep 29, 2023CVE 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=11.11 <16.2.8
- Affected versionversion=16.3 <16.3.5
- Affected versionversion=16.4 <16.4.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.
Public exploit references
- Public SSO-bypass reproduction stepsproof of concept · demonstrated
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