CVE-2026-4922

Cross-Site Request Forgery (CSRF) in GitLab

Published Apr 22, 2026 CVSS 3.1 · 8.1 High EPSS < 1% KEV · Not listed
Description
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.

Analysis

AI-generated

Technical impact

GitLab contained a CSRF flaw that allowed an unauthenticated user to trigger GraphQL mutations on behalf of any logged‑in user. Because the mutation endpoint accepted requests without a CSRF token, an attacker could cause the victim to change settings, delete data, or otherwise perform privileged actions. The weakness is a classic CSRF vulnerability (CWE‑352).

Affected Systems

The flaw affects GitLab CE/EE from version 17.0 through the release immediately before 18.9.6, from 18.10.0 to just before 18.10.4, and from 18.11.0 to just before 18.11.1. All other supported releases are unaffected.

Risk and Exploitability

The CVSS score of 8.1 indicates a high severity. EPSS is not available, so the likelihood of exploitation is unknown, but the flaw is listed outside the KEV catalog. Based on the description, it is inferred that the attacker would deliver a crafted GraphQL mutation request from a malicious site to an authenticated victim's browser. The likely attack vector thus involves a victim already logged in visiting a site that submits a mutation request without a CSRF token, causing the action to execute with the victim's privileges. Given the high impact and lack of mitigation in those versions, the risk to exposed installations is significant.

Remediation

Vendor Solution

Upgrade to versions 18.9.6, 18.10.4, 18.11.1 or above.


OpenCVE Recommended Actions

  • Upgrade all GitLab installations to at least the patched releases: 18.9.6, 18.10.4, 18.11.1, or newer.
  • Restart or reload the GitLab services to apply the new codebase.
  • Verify that no custom plugins or integrations expose the GraphQL endpoint without CSRF protection and consider disabling or updating any such extensions.

Generated by OpenCVE AI on April 27, 2026 at 08:34 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
CPEs cpe:2.3:a:gitlab:gitlab:*:*:*:*:community:*:*:*
cpe:2.3:a:gitlab:gitlab:*:*:*:*:enterprise:*:*:*
cpe:2.3:a:gitlab:gitlab:18.11.0:*:*:*:community:*:*:*
cpe:2.3:a:gitlab:gitlab:18.11.0:*:*:*:enterprise:*:*:*
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'total'}, 'version': '2.0.3'}

Type Values Removed Values Added
Description 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.
Title Cross-Site Request Forgery (CSRF) in GitLab
First Time appeared Gitlab
Gitlab gitlab
Weaknesses CWE-352
CPEs cpe:2.3:a:gitlab:gitlab:*:*:*:*:*:*:*:*
Vendors & Products Gitlab
Gitlab gitlab
References
Metrics cvssV3_1

{'score': 8.1, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N'}

Weaknesses
  • CWE-352

    Cross-Site Request Forgery (CSRF)

Sources

Status
PUBLISHED
Assigner
GitLab
Published
Updated
Apr 24, 2026, 3:55 AM
Reserved
Mar 26, 2026, 6:03 PM
Status
Analyzed
Published
Apr 22, 2026, 5:16 PM
Modified
Nov 11, 2026, 11:10 PM