Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:NCVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.
Summary
CVE-2026-4922 is a high-severity CSRF (CWE-352) vulnerability in Gitlab Gitlab. Its CVSS base score is 8.1 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked at the 12th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.
The strongest mitigations our analysis identified map to AC-3 (Access Enforcement) and SC-23 (Session Authenticity) — see the control section below for these in your framework.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
CVE-2026-4922 is a cross-site request forgery (CSRF) vulnerability, classified under CWE-352, affecting GitLab Community Edition (CE) and Enterprise Edition (EE) in all versions from 17.0 prior to 18.9.6, 18.10 prior to 18.10.4, and 18.11 prior to 18.11.1. The flaw stems from insufficient CSRF protection, enabling an unauthenticated user to execute GraphQL mutations on behalf of authenticated users. It carries a CVSS v3.1 base score of 8.1 (AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N), indicating high severity due to network accessibility, low complexity, and significant impacts on confidentiality and integrity.
An unauthenticated attacker can exploit this vulnerability by tricking an authenticated GitLab user into interacting with a malicious resource, such as clicking a crafted link or visiting a malicious webpage. This user interaction (UI:R) allows the attacker to forge requests that execute unauthorized GraphQL mutations with the victim's elevated privileges, potentially enabling actions like data modification, access to sensitive information, or other privilege-escalating operations depending on the targeted mutations and user permissions.
GitLab has remediated the issue through patch releases, as detailed in the advisory for GitLab 18.11.1 and referenced in the associated work item and HackerOne report. Affected instances should be upgraded to GitLab 18.9.6, 18.10.4, 18.11.1, or later versions to mitigate the vulnerability.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2026-25040
Vulnerability Data
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…
more
insufficient CSRF protection.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V3.3.2V3.5.1V10.2.1
Mitigating Controls (NIST 800-53 r5) AI
Access enforcement requires verifying that state-changing requests originate from the authenticated user rather than a forged cross-site source.
Protecting session authenticity prevents attackers from replaying or forging authenticated requests via the victim's browser.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Secure SDLC practices directly require anti-CSRF controls such as tokens or SameSite attributes.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
By denying access to phishing or malicious sites, the control lowers the likelihood that a user will be tricked into submitting a forged request that performs an unintended action on another site.