CVE Watchtower

CVE-2024-9512Gitlab Gitlab

NVDCVSS scored by cve@gitlab.com

Vulnerability Summary

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.
Severity Level
MEDIUM(5.3)
Published Date
Jun 12, 2025
Last Modified
Aug 8, 2025
Exploitation Status
No confirmed exploitation yet
Root Weakness (CWE)
See the MITRE CWE entry for the full definition of this weakness.
CVSS v3.1 Base Metrics — Score 5.3 (MEDIUM)
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N
Attack VectorNetwork
Attack ComplexityHigh
Privileges RequiredLow
User InteractionNone
ScopeUnchanged
ConfidentialityHigh
IntegrityNone
AvailabilityNone

Affected & Patched Versions

Affected Versions
  • Gitlab Gitlab < 17.10.8
  • Gitlab Gitlab >= 17.11.0 and < 17.11.4
  • Gitlab Gitlab >= 18.0.0 and < 18.0.2
Patched Versions
  • Gitlab Gitlab 17.10.8
  • Gitlab Gitlab 17.11.4
  • Gitlab Gitlab 18.0.2

What to do

Fix it during your normal patch cycle. No exploitation is confirmed yet.

  1. Check whether you run Gitlab Gitlab and which version.
  2. Update to a patched version listed above, then confirm the new version.

Timeline

  • Jun 12, 2025Published
  • Aug 8, 2025Record last modified

Score, severity and exploitation changes are tracked from the day Watchtower started logging them.

Get notified about new GitLab CVEsYou are reading CVE-2024-9512. Get an email when KEV listings, exploits or new CVEs match your stack.
Notify me about GitLab CVEs

Data last checked: Nov 19, 2026 04:06 UTC