CVE-2026-19650: CSRF in GitLab CE/EE GraphQL Multiplex Query Handling
- Vendor
- GitLab
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.
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.
Exploits
1 exploit validated by Mallory's analysis. Hidden: 1 rejected by Mallory's analysis as not a working exploit.
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.
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.
Recent activity
34 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.