CVE-2026-4922: 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.

CVE-2026-4922 · Severity: high · CVSS 8.1 · Published 2026-04-22

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.

Technologies: GitLab. Vendors: GitLab.

Quick answers

Is CVE-2026-4922 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-4922 being exploited in the wild.
How severe is CVE-2026-4922?
High severity, with a CVSS score of 8.1, published 22 April 2026.
Which products and versions are affected?
GitLab. The advisory does not name versions.
Is there a fix for CVE-2026-4922?
No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
Am I affected by CVE-2026-4922?
Check whether you run GitLab. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Affected products

  • GitLab

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.