Internal repository disclosure via non-external policy bots
Published Dec 1, 2023 · Updated Nov 20, 2025
Improper authorization in GitLab EE 16.2 through 16.4.2, 16.5 through 16.5.2, and 16.6.0 allows remote authenticated users to clone internal projects. The bot creation service marks security policy bots as regular rather than external users, so captured bot CI job tokens inherit access that external users lack. Exploitation requires an external project Owner, or a Maintainer when a bot already exists, and a controlled runner that captures the token.
Summary
What happened
Improper authorization in GitLab EE 16.2 through 16.4.2, 16.5 through 16.5.2, and 16.6.0 allows remote authenticated users to clone internal projects. The bot creation service marks security policy bots as regular rather than external users, so captured bot CI job tokens inherit access that external users lack. Exploitation requires an external project Owner, or a Maintainer when a bot already exists, and a controlled runner that captures the token.
The record
- CVE
- CVE-2023-5995
- Published
- Dec 1, 2023
- Updated
- Nov 20, 2025
- Vendor
- GitLab
- Product
- GitLab
- Classifications
- CWE-863, T1078
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Dec 1, 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=16.2 <16.4.3
- Affected versionversion=16.5 <16.5.3
- Affected versionversion=16.6 <16.6.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
- Policy-bot CI token 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