CVE-2025-1516 Allocation of Resources Without Limits or Throttling in GitLab
Attackers can cause a denial of service in GitLab by exploiting improper input validation in token names.
- 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-2025-1516?
CVE-2025-1516 is a medium-severity denial of service vulnerability in Gitlab Gitlab, published on 12 Jun 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Official description
An issue has been discovered in GitLab CE/EE affecting all versions from 8.7 before 17.10.8, 17.11 before 17.11.4, and 18.0 before 18.0.2. Improper input validation in Tokens Names could be used to trigger a denial of service.
Weakness: CWE-770
Which versions are affected by CVE-2025-1516?
1 open source package ship an affected version, including gitlab. It affects 1 product.
| Package | Affected | Fixed in |
|---|---|---|
gitlab Bitnami | From 8.7.0 | 18.0.2 |
Products include Gitlab Gitlab.
How do I fix CVE-2025-1516?
Upgrade gitlab to 18.0.2 or later.
Upgrade, then put limits on request size, rate and nesting depth so one client cannot exhaust the service. More about Denial of service.
Is CVE-2025-1516 being exploited?
There is no known exploitation of CVE-2025-1516 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-2025-1516, GHSA-r66m-9f9x-jv46, UBUNTU-CVE-2025-1516.