GitLab Community Edition/Enterprise Edition up to 18.9.5/18.10.3/18.11.0 GraphQL Mutation cross-site request forgery
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.1 | $0-$5k | 2.95 |
Summary
A vulnerability was found in GitLab Community Edition and Enterprise Edition up to 18.9.5/18.10.3/18.11.0 and classified as problematic. Impacted is an unknown function of the component GraphQL Mutation Handler. The manipulation results in cross-site request forgery. This vulnerability is cataloged as CVE-2026-4922. The attack may be launched remotely. There is no exploit available. It is suggested to upgrade the affected component.
Details
A vulnerability was found in GitLab Community Edition and Enterprise Edition up to 18.9.5/18.10.3/18.11.0. It has been classified as problematic. Affected is an unknown code of the component GraphQL Mutation Handler. The manipulation with an unknown input leads to a cross-site request forgery vulnerability. CWE is classifying the issue as CWE-352. The web application does not, or can not, sufficiently verify whether a well-formed, valid, consistent request was intentionally provided by the user who submitted the request. This is going to have an impact on integrity. CVE summarizes:
GitLab has remediated an issue in GitLab CE/EE affecting all versions from 17.0 before 18.9.6, 18.10 before 18.10.4, and 18.11 before 18.11.1 that could have allowed an unauthenticated user to execute GraphQL mutations on behalf of authenticated users due to insufficient CSRF protection.
The weakness was shared by ahacker1. The advisory is available at gitlab.com. This vulnerability is traded as CVE-2026-4922 since 03/26/2026. The exploitability is told to be easy. It is possible to launch the attack remotely. The exploitation doesn't require any form of authentication. Successful exploitation requires user interaction by the victim. The technical details are unknown and an exploit is not available.
Upgrading to version 18.9.6, 18.10.4 or 18.11.1 eliminates this vulnerability.
The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2026-25040). If you want to get best quality of vulnerability data, you may have to visit VulDB.
Product
Type
Vendor
Name
Version
- 18.0
- 18.1
- 18.2
- 18.3
- 18.4
- 18.5
- 18.6
- 18.7
- 18.8
- 18.9
- 18.9.0
- 18.9.1
- 18.9.2
- 18.9.3
- 18.9.4
- 18.9.5
- 18.10
- 18.10.0
- 18.10.1
- 18.10.2
- 18.10.3
- 18.11.0
License
Website
- Vendor: https://gitlab.com/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.2VulDB Meta Temp Score: 6.1
VulDB Base Score: 4.3
VulDB Temp Score: 4.1
VulDB Vector: 🔒
VulDB Reliability: 🔍
CNA Base Score: 8.1
CNA Vector (GitLab): 🔒
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Cross-site request forgeryCWE: CWE-352 / CWE-862 / CWE-863
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: Community Edition/Enterprise Edition 18.9.6/18.10.4/18.11.1
Timeline
03/26/2026 CVE reserved04/22/2026 Advisory disclosed
04/22/2026 VulDB entry created
04/22/2026 VulDB entry last update
Sources
Vendor: gitlab.comAdvisory: gitlab.com
Researcher: ahacker1
Status: Confirmed
CVE: CVE-2026-4922 (🔒)
GCVE (CVE): GCVE-0-2026-4922
GCVE (VulDB): GCVE-100-359034
EUVD: 🔒
Entry
Created: 04/22/2026 19:05Updated: 04/22/2026 21:25
Changes: 04/22/2026 19:05 (66), 04/22/2026 21:25 (1)
Complete: 🔍
Cache ID: 216::103
If you want to get best quality of vulnerability data, you may have to visit VulDB.
No comments yet. Languages: en.
Please log in to comment.