CVE-2026-19650
Cross-Site Request Forgery (CSRF) in GitLab
No known exploitation. EPSS puts it in the 48th percentile. Fixed versions are out.
What to do
Find your product and version, then upgrade to the build on the right.
- GitLabAffected: ≥ 18.2, < 18.11.11Upgrade to: 18.11.11Affected: ≥ 19.0, < 19.0.8Upgrade to: 19.0.8Affected: ≥ 19.1, < 19.1.6Upgrade to: 19.1.6Affected: ≥ 19.2, < 19.2.4Upgrade to: 19.2.4Stated by: CVE record
Versions as the sources state them. Full version matrix after sign-in
Coverage timeline
6 publishersVendor patch released
Sourced from public security reporting — each date is when it was published, not when it happened.
What it is
From the CVE record
GitLab has remediated an issue in GitLab CE/EE affecting all versions from 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 that under certain conditions could have allowed an unauthenticated user to execute mutations via GET requests due to improper request validation in GraphQL multiplex query handling.
In plain language
No plain-language summary for this CVE yet.
Exploitation
Where each signal puts this CVE on the scale from published to confirmed exploited.
- CISA KEV
Not in the catalog. CISA has not confirmed exploitation.
- Public exploits
No public exploit or proof of concept found in the sources we track.
- EPSS
0.6% chance of exploitation activity in the next 30 days, which ranks it in the 48th percentile of scored CVEs.
Exploit Prediction Scoring System, FIRST.org. A probability, not a confirmation.
Lifecycle
10 events over 16 days, from the signal feeds we watch.
- Patch availablerecord updated
- OpenVAS check added
- Patch availablerecord updated
- Patch availablepublished, weakness classified, att&ck mapped, record updated
Affected products
And 1 more affected product. See all after sign-in
Technical detail
CVSS 3.1 vector
Open in the CVSS calculatorCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:L
Scored 7.1 by NVD.
How it is reached
- Attack Vector NetworkExploitable remotely over the network without any special conditions
- Attack Complexity LowNo special conditions — the attack can be reliably reproduced
- Privileges Required NoneNo authentication required — anyone can exploit this
- User Interaction RequiredA user must click a link, open a file, or perform some action
Scope
- Scope UnchangedImpact is limited to the vulnerable component itself
Impact if exploited
- Confidentiality NoneNo confidentiality impact
- Integrity HighTotal loss of integrity — attacker can modify any data in the component
- Availability LowReduced performance or intermittent disruption of service
Weaknesses
ATT&CK techniques
Mapped from the weaknesses above (CWE to ATT&CK), not observed in attacks.
- Initial AccessT1189Drive-by Compromisemedium confidence
Sources
References in the record
In the news
- Критическая уязвимость в GitLab позволяла удалять общедоступные проекты
- Critical GitLab Zero-Click Flaw Poses Mitigation Challenges
- Critical and High-Severity GraphQL CVEs in GitLab: Code Injection and CSRF via One Directive
- Critical GitLab flaw allows attackers to modify or delete public projects (CVE-2026-19478)
- GitLab Patches Critical Code Injection Vulnerability
- Critical GitLab GraphQL Flaw Could Let Unauthenticated Attackers Delete Public Projects
Watch the software you run.
My Stack ranks new CVEs for your products by real-world exploitation, so the next serious one reaches you without reading every advisory.
We'll flag the next CVE, public exploit or patch for GitLab, not every advisory.
A free account adds
- The full version matrix and every affected product
- Exploit links, proofs of concept and Metasploit modules
- Email alerts for the products you watch
- The same data over REST API, MCP and CLI