CVE-2024-10925 Authorization Bypass Through User-Controlled Key in GitLab
Guest users can bypass authorization checks to read Security policy YAML files in GitLab Enterprise Edition.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2024-10925?
CVE-2024-10925 is a medium-severity missing authorization vulnerability in Gitlab Gitlab, published on 3 Mar 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Official description
A vulnerability in GitLab-EE affecting all versions from 16.2 prior to 17.7.6, 17.8 prior to 17.8.4, and 17.9 prior to 17.9.1 allows a Guest user to read Security policy YAML
Weakness: CWE-639
Which versions are affected by CVE-2024-10925?
1 open source package ship an affected version, including gitlab. It affects 1 product.
| Package | Affected | Fixed in |
|---|---|---|
gitlab Bitnami | From 16.2.0 | 17.9.1 |
Products include Gitlab Gitlab.
How do I fix CVE-2024-10925?
Upgrade gitlab to 17.9.1 or later.
Upgrade, and check permissions on every request on the server, not only in the interface. More about Missing authorization.
Is CVE-2024-10925 being exploited?
There is no known exploitation of CVE-2024-10925 in the wild and no public exploit code.
Other vulnerabilities in Gitlab Gitlab
- CVE-2026-97229 GitLab Community Edition and Enterprise Edition Integer Overflow or Wraparound
- CVE-2026-85706 GitLab Community Edition and Enterprise Edition Path Traversal
- CVE-2023-7028 GitLab Community and Enterprise Editions Improper Access Control
- CVE-2021-22205 GitLab Community and Enterprise Editions Remote Code Execution
- CVE-2021-39935 GitLab Community and Enterprise Editions Server-Side Request Forgery (SSRF)
Sources
Also known as BIT-gitlab-2024-10925.