CVE-2025-1754: Missing Authentication for Critical Function in GitLab
An issue has been discovered in GitLab CE/EE affecting all versions from 17.2 before 17.11.5, 18.0 before 18.0.3, and 18.1 before 18.1.1 that could have allowed unauthenticated attackers to upload arbitrary files to public projects by sending crafted API requests, potentially leading to resource abuse and unauthorized content storage.
Other sources
GitLab has remediated an issue that could have allowed unauthenticated attackers to upload arbitrary files to public projects by sending crafted API requests, potentially leading to resource abuse and unauthorized content storage.
— GitLab
Affected Software
Remediation
Information
Event History
Peer vulnerabilities
Found alongside the following vulnerabilities.
Frequently Asked Questions
What is the severity of CVE-2025-1754?
CVE-2025-1754 is considered a high severity vulnerability due to its potential to allow unauthenticated attackers to upload arbitrary files.
How do I fix CVE-2025-1754?
To fix CVE-2025-1754, upgrade GitLab to version 17.11.5 or later, 18.0.3 or later, or 18.1.1 or later.
Which versions of GitLab are affected by CVE-2025-1754?
CVE-2025-1754 affects GitLab versions from 17.2 to prior to 17.11.5, 18.0 to prior to 18.0.3, and 18.1 to prior to 18.1.1.
What can attackers do with the vulnerability CVE-2025-1754?
With CVE-2025-1754, attackers can exploit the vulnerability to upload arbitrary files to public projects.
Is authentication required to exploit CVE-2025-1754?
No, CVE-2025-1754 can be exploited by unauthenticated users, which increases its risk.