CVE-2026-4922
CSRF Vulnerability in GitLab Allows Unauthorized GraphQL Mutation Execution
Publication date: 2026-04-22
Last updated on: 2026-04-23
Assigner: GitLab Inc.
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| gitlab | gitlab | From 18.10.0 (inc) to 18.10.4 (exc) |
| gitlab | gitlab | From 18.10.0 (inc) to 18.10.4 (exc) |
| gitlab | gitlab | From 17.0.0 (inc) to 18.9.6 (exc) |
| gitlab | gitlab | From 17.0.0 (inc) to 18.9.6 (exc) |
| gitlab | gitlab | 18.11.0 |
| gitlab | gitlab | 18.11.0 |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-352 | The web application does not, or cannot, sufficiently verify whether a request was intentionally provided by the user who sent the request, which could have originated from an unauthorized actor. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability in GitLab CE/EE versions before certain fixed releases allows an unauthenticated user to execute GraphQL mutations on behalf of authenticated users. The root cause is insufficient Cross-Site Request Forgery (CSRF) protection, which means attackers could trick authenticated users into performing unintended actions without their consent.
How can this vulnerability impact me? :
The impact of this vulnerability is high because an attacker can perform actions with the privileges of an authenticated user without needing to authenticate themselves. This could lead to unauthorized changes or data manipulation within GitLab, compromising confidentiality and integrity of data.
What immediate steps should I take to mitigate this vulnerability?
To mitigate this vulnerability, you should upgrade GitLab CE/EE to a fixed version. Specifically, update to version 18.9.6 or later if you are on the 17.0 to before 18.9.6 range, to 18.10.4 or later if you are on 18.10 before 18.10.4, or to 18.11.1 or later if you are on 18.11 before 18.11.1.
This vulnerability is due to insufficient CSRF protection allowing unauthenticated users to execute GraphQL mutations on behalf of authenticated users, so applying the official patches or upgrades from GitLab is the recommended immediate step.