Vulnerabilities

Vulnerability · CVE-2024-9512

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.

Published Jun 12, 2025 · catalog updated Jun 12, 2025 · GitLab GitLab

Check this week

CVE-2024-9512 is not in CISA KEV. FIRST estimates a 25.00% chance of exploitation in the next 30 days. Check whether you run GitLab GitLab.

Gaps on this record

  • No vendor fix or required action is stored. Compare the linked advisory before you change production.
Severity
Medium5.3
Known exploitation
Not in CISA/VulnCheck KEV
EPSS
25.00%
Remediation
Version ranges on file
Affected products
vendor GitLab GitLab 17.11 <17.11.4

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.

Are you affected?

Enter the version you run. The result uses only the ranges stored on this record.

The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.

  • vendor GitLab GitLab 17.11 <17.11.417.11 <17.11.4

How to fix CVE-2024-9512

What to do

Three questions, each answered from this record only. Confirm the vendor advisory before you patch.

Should you patch?

CVE-2024-9512 is not in CISA KEV. FIRST estimates a 25.00% chance of exploitation in the next 30 days. Check whether you run GitLab GitLab.

Which versions are affected?

Compare what you have installed with GitLab GitLab 17.11 <17.11.4 17.11 <17.11.4. Compare the installed version with the linked vendor advisory before you change production.

What should an analyst verify?

No weakness class is stored. EPSS 25.00%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.

Code

The project this record applies to. Exploit listings stay in References.

Timeline

Detection, updates, and resolution for this record.

  1. Jun 12, 2025 · EUVD

    Detected

    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.

  2. Jun 12, 2025 · EUVD

    Updated

    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.

Sources

  • CVE.orgVulnerability recordCVE-2024-9512

    Official CVE identifier

    cve.org
  • EUVDVulnerability recordEUVD-2024-54676

    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.

    euvd.enisa.europa.eu

References

Freshness

Last verified in this catalog Oct 18, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.