An issue has been discovered in GitLab EE affecting all versions prior to 17.10.8, 17.11 prior to 17.11.4, and 18.0 prior to 18.0.2. It may have been possible for private repository to be cloned in case of race condition when a secondary node is out of sync.
CVE-2024-9512
MEDIUMNVD 5.3
5.3
- CVSS v3
- 5.3
- EG Score
- —
- EPSS
- —
- KEV
- Not listed
Published
June 12, 2025
Last Modified
August 8, 2025
References (2)
Vendor Advisories for CVE-2024-9512(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Frequently asked(4)
What is CVE-2024-9512?
CVE-2024-9512 is a medium vulnerability published on June 12, 2025. An issue has been discovered in GitLab EE affecting all versions prior to 17.10.8, 17.11 prior to 17.11.4, and 18.0 prior to 18.0.2. It may have been possible for private repository to be cloned in case of race condition when a secondary node is out of sync.
When was CVE-2024-9512 disclosed?
CVE-2024-9512 was first published in the National Vulnerability Database on June 12, 2025, with the most recent update on August 8, 2025. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
What is the CVSS score of CVE-2024-9512?
CVE-2024-9512 has a CVSS v3 base score of 5.3 (NVD).
How do I remediate CVE-2024-9512?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2024-9512, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2024-9512
Is Your Infrastructure Affected by CVE-2024-9512?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.