Skip to main content
Mallory
HighVulnerability

CVE-2026-4922: CSRF in GitLab GraphQL API

Published Apr 22, 2026 · Updated 2 months ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS8.1High · v3.1
EPSS0.27%19th percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
Vendor
GitLab
IdentifiersCVE-2026-4922CWE-352 · Cross-Site Request Forgery (CSRF)

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.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation allows unauthorized state-changing actions within the scope of the victim user’s GitLab permissions. Depending on the victim’s role and accessible GraphQL mutations, this can include modifying repository settings, changing project configuration, updating account details, and performing other writable operations. The vulnerability has high confidentiality and integrity impact because mutation responses may expose sensitive data and because attackers can cause unauthorized changes as the victim. No direct availability impact has been identified.

Mitigation

If you can’t patch tonight, do this now.

If immediate upgrade is not possible, reduce exposure by limiting access to GitLab to trusted users and networks, minimizing active authenticated browser sessions, and restricting opportunities for users to be lured to attacker-controlled web content while logged in. Administrative controls such as isolating management access, using separate browsers or browser profiles for GitLab administration, and enforcing user awareness around unsolicited links can reduce exploitability. These measures are compensating controls only; no complete workaround is currently available in the provided information.

Remediation

Patch, then assume compromise.

Upgrade self-managed GitLab CE/EE instances to a fixed release: 18.9.6, 18.10.4, 18.11.1, or a later version. GitLab’s fix strengthens request-origin verification and rejects GraphQL mutation requests that do not satisfy anti-forgery validation requirements. Where applicable, follow GitLab’s documented upgrade procedures; patch releases may include database migrations, which can require downtime on single-node deployments.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
GitLabGitlabapplication
FAQ

Frequently asked questions

Is CVE-2026-4922 exploited in the wild?
As of Sep 25, 2026, Mallory has no reports of CVE-2026-4922 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-4922?
As of Sep 25, 2026, Mallory has found no public exploit for CVE-2026-4922.
Is there a patch for CVE-2026-4922?
Upgrade self-managed GitLab CE/EE instances to a fixed release: 18.9.6, 18.10.4, 18.11.1, or a later version. GitLab’s fix strengthens request-origin verification and rejects GraphQL mutation requests that do not satisfy anti-forgery validation requirements.
What products are affected by CVE-2026-4922?
Gitlab.
How severe is CVE-2026-4922?
CVE-2026-4922 has a CVSS v3.1 score of 8.1 (High) and an EPSS score of 0.27% (19th percentile) as of Sep 25, 2026.
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity7Community discussion across Reddit, Mastodon, and other social sources.