CVE-2025-1540: Incorrect Authorization in GitLab
An issue has been discovered in GitLab CE/EE for Self-Managed and Dedicated instances affecting all versions from 17.5 prior to 17.6.5, 17.7 prior to 17.7.4, and 17.8 prior to 17.8.2. It was possible for a user added as an External to read and clone internal projects under certain circumstances."
Other sources
An issue has been discovered in GitLab CE/EE for Self-Managed and Dedicated instances affecting all versions from 17.5 prior to 17.6.5, 17.7 prior to 17.7.4, and 17.8 prior to 17.8.2. It was possible for a user manually designated as an External without configuring them as such in SAML response to lose that designation, and to read and clone internal projects under certain circumstances. After upgrading to a patched version, please review and re-designate any externals users. This is a low severity issue (CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:N/A:N, 3.1). It is now mitigated in the latest release and is assigned CVE-2025-1540.
— GitLab
Affected Software
Remediation
Information
Event History
Peer vulnerabilities
Found alongside the following vulnerabilities.
Frequently Asked Questions
What is the severity of CVE-2025-1540?
CVE-2025-1540 is considered a critical vulnerability due to its potential to expose internal projects to unauthorized users.
How do I fix CVE-2025-1540?
To fix CVE-2025-1540, upgrade GitLab CE/EE to version 17.6.5, 17.7.4, or 17.8.2 or later.
Who is affected by CVE-2025-1540?
CVE-2025-1540 affects all instances of GitLab CE/EE versions from 17.5 prior to 17.6.5, 17.7 prior to 17.7.4, and 17.8 prior to 17.8.2.
What types of projects are vulnerable due to CVE-2025-1540?
CVE-2025-1540 allows external users to read and clone internal projects in specific scenarios.
Is there a workaround for CVE-2025-1540?
No official workaround is recommended; the best course of action is to update GitLab to a patched version.