CVE-2026-4922 is a cross-site request forgery vulnerability in GitLab CE/EE affecting the GraphQL API, specifically state-changing mutation operations exposed through the GraphQL endpoint. The flaw stems from insufficient CSRF protection and inadequate validation of the origin of mutation requests, allowing the endpoint to accept requests authenticated only by the victim’s existing session cookies without enforcing proper anti-forgery checks. As a result, an unauthenticated attacker can induce a logged-in GitLab user to submit forged GraphQL mutation requests that execute under that user’s identity. Affected versions are all GitLab CE/EE releases from 17.0 before 18.9.6, 18.10 before 18.10.4, and 18.11 before 18.11.1.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
12 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A GitLab CE/EE vulnerability caused by insufficient CSRF protection that could allow an unauthenticated attacker to execute GraphQL mutations as authenticated users.
A high-severity CSRF vulnerability in GitLab's GraphQL API (/api/graphql) that allows an authenticated user who visits a malicious web page to unknowingly execute GraphQL mutations against their GitLab instance using their session.
A high-severity CSRF vulnerability in GitLab's GraphQL API that could allow unauthenticated attackers to execute GraphQL mutations on behalf of authenticated users.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.