Private repository disclosure via stale secondary state
Published Jun 12, 2025 · Updated Jun 12, 2025
Disclosure in GitLab before 17.10.8, 17.11 before 17.11.4, and 18.0 before 18.0.2 allows remote authenticated users to clone private repositories. A secondary node handles a precisely timed clone while its replicated state is stale, creating a check/use race that serves repository contents. The attack requires a valid low-privilege account, a Geo secondary node, and a replication-lag window; the consequence is limited to reading private repository data.
Summary
What happened
Disclosure in GitLab before 17.10.8, 17.11 before 17.11.4, and 18.0 before 18.0.2 allows remote authenticated users to clone private repositories. A secondary node handles a precisely timed clone while its replicated state is stale, creating a check/use race that serves repository contents. The attack requires a valid low-privilege account, a Geo secondary node, and a replication-lag window; the consequence is limited to reading private repository data.
The record
- CVE
- CVE-2024-9512
- Published
- Jun 12, 2025
- Updated
- Jun 12, 2025
- Vendor
- GitLab
- Product
- GitLab
- Classifications
- CWE-367, T1213.003
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 12, 2025CVE publishedPublication date reported by the CVE source.
- Jun 12, 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 <17.10.8
- Affected versionversion=17.11 <17.11.4
- Affected versionversion=18.0 <18.0.2
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