Track vulnerabilities like this one.
Sign up free to get alerted when software you use is affected.
8.1
CVE-2024-4994: GitLab lets attackers change data through forged web requests
CVE-2024-4994 · published 1 year ago
Summary
Versions of GitLab Community and Enterprise Edition from 16.1 up to 16.11.4 and early 17.x releases are vulnerable. An attacker could trick a logged‑in user into sending a specially crafted request that makes unwanted changes to your GitLab data. Update to the latest GitLab release or apply the provided patches to block these forged requests.
What to do
The CVE record does not list a fixed version. Check the vendor's site or the advisory links below - a fix may already be released.
Affected software
| Vendor | Product | Affected versions |
|---|---|---|
| gitlab | gitlab |
>= 16.1.0, < 16.11.5 >= 17.0.0, < 17.0.3 17.1.0 cpe:2.3:a:gitlab:gitlab:*:*:*:*:community:*:*:* |
Original advisory text
Cross-Site Request Forgery (CSRF) in GitLab
An issue has been discovered in GitLab CE/EE affecting all versions from 16.1.0 before 16.11.5, all versions starting from 17.0 before 17.0.3, all versions starting from 17.1.0 before 17.1.1 which allowed for a CSRF attack on GitLab's GraphQL API leading to the execution of arbitrary GraphQL mutations.
References
- https://gitlab.com/gitlab-org/gitlab/-/issues/462012 Third Party Advisory
- https://hackerone.com/reports/2473644 Third Party Advisory
- https://github.com/CVEProject/cvelistV5/tree/main/cves/2024/4xxx/CVE-2024-4994.j... Vendor Advisory
- https://nvd.nist.gov/vuln/detail/CVE-2024-4994 Vendor Advisory
Internet-facing
14 days
Internal
At next upgrade
- Not known to be exploited
- Needs hands-on effort to exploit
- Gives an attacker full control
Type
CWE-352Cross-Site Request Forgery (CSRF)
Timeline
Published20 Jun 2025
Updated4 Nov 2026
First seen7 Mar 2026
Track software like this
Free during beta