Skip to main content
Mallory
HighPublic exploitVulnerability

CVE-2026-19650: CSRF in GitLab CE/EE GraphQL Multiplex Query Handling

Published Aug 17, 2026 · Updated 9 days ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 days1 mention · peak 1 in a dayToday
CVSS7.1High · v3.1
EPSS0.21%12th percentile
CISA KEVNoNot listed
In the wildReported1 exploitation record in Mallory
Vendor
GitLab
IdentifiersCVE-2026-19650CWE-352 · Cross-Site Request Forgery (CSRF)

CVE-2026-19650 is a cross-site request forgery vulnerability in GitLab Community Edition and Enterprise Edition caused by improper validation of multiplexed GraphQL requests. IntroducedTracer stores query-document and future-field state in shared instance variables that can be overwritten while parsing multiple queries. Consequently, execute_query can execute a different document from the one validated, bypassing the restriction that GraphQL GET requests perform only read-only operations. An unauthenticated attacker can induce an authenticated victim's browser to submit a crafted GET request that executes a state-changing mutation. Affected versions are 18.2 before 18.11.11, 19.0 before 19.0.8, 19.1 before 19.1.6, and 19.2 before 19.2.4. The vulnerability has a CVSS v3.1 score of 7.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 permits unauthorized state-changing GraphQL operations using the victim's authenticated session, including changes to project settings. The scope of accessible operations depends on the victim's permissions; targeting an administrator can expose instance-level administrative operations. The published CVSS vector, CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:L, rates integrity impact as high, availability impact as low, and confidentiality impact as none. Arbitrary operating-system command execution is not established for this vulnerability.

Mitigation

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

No vendor-documented configuration workaround is established; upgrading is the definitive remediation. If patching is delayed, restrict access to the GraphQL API where operationally feasible and reduce public exposure by placing the instance behind a VPN or equivalent access controls. These measures reduce exposure but do not correct the validation flaw or necessarily prevent CSRF against users who retain access.

Remediation

Patch, then assume compromise.

Upgrade affected self-managed GitLab CE/EE installations to 18.11.11, 19.0.8, 19.1.6, or 19.2.4 in the corresponding release branch, or to a later supported fixed release. Installations on branches 18.2 through 18.10 must move to a supported patched branch. The fix replaces shared tracer state with per-query data keyed to the filtered document and permits document substitution only when a matching entry exists. GitLab.com and GitLab Dedicated were already patched at disclosure and required no customer action.

Public exploits

Exploits

1 exploit validated by Mallory's analysis. Hidden: 1 rejected by Mallory's analysis as not a working exploit.

View more in app →
gitlab-cve-2026-19478-labRepository is a small self-contained GitLab vulnerability lab and PoC set with 5 files: a README, Docker Compose lab definition, two Python PoCs, and a Bash setup script. The main exploit file, poc_cve_2026_19478.py, targets CVE-2026-19478 in GitLab GraphQL. It sends POST requests to /api/graphql with attacker-controlled GraphQL fields annotated by @gl_introduced(version:"99.0.0") so that on vulnerable servers the fallback path resolves the field by calling object.public_send(field_name). In safe mode it probes with a harmless zero-argument method such as to_param against a public project and treats a non-null response as evidence of arbitrary method invocation. In optional proof mode, it first uses the authenticated REST API (/api/v4/projects) to create a disposable public project, then sends an unauthenticated GraphQL query requesting the destroy field to trigger Project#destroy, and finally verifies deletion via GET /api/v4/projects/{id}. This demonstrates unauthenticated destructive impact against public projects. The second PoC, poc_cve_2026_19650.py, is a safe detector for the sibling CVE-2026-19650. It submits a two-element Apollo-style GraphQL batch to /api/graphql and checks whether slot 0 incorrectly returns slot 1 data, indicating multiplex query/document swapping caused by shared tracer state. The repository also includes docker-compose.yml, which provisions two GitLab CE containers for A/B testing: vulnerable 19.2.2-ce.0 on port 8222 and patched 19.2.4-ce.0 on port 8224. setup.sh waits for GraphQL readiness, seeds a public project at root/pub, and creates an admin personal access token on each instance for lab use. Overall, this is a real exploit repository with both detection and optional impact-proof capability, focused on unauthenticated GraphQL abuse in GitLab rather than a generic scanner or framework module.dinosn · Disclosed Aug 18, 2026 · markdown · yaml · web · networkOperational
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-19650 exploited in the wild?
Yes. As of Nov 8, 2026, Mallory has reports of exploitation in the wild.
Is there a public exploit for CVE-2026-19650?
Yes. Mallory tracks 1 public exploit or proof of concept for CVE-2026-19650, the earliest disclosed Aug 18, 2026.
Is there a patch for CVE-2026-19650?
Upgrade affected self-managed GitLab CE/EE installations to 18.11.11, 19.0.8, 19.1.6, or 19.2.4 in the corresponding release branch, or to a later supported fixed release. Installations on branches 18.2 through 18.10 must move to a supported patched branch.
What products are affected by CVE-2026-19650?
Gitlab.
How severe is CVE-2026-19650?
CVE-2026-19650 has a CVSS v3.1 score of 7.1 (High) and an EPSS score of 0.21% (12th percentile) as of Nov 8, 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 activity10Community discussion across Reddit, Mastodon, and other social sources.