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… (CVE-2026-19650)
A vulnerability in GitLab CE/EE 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 allows an unauthenticated user to execute mutations via GET requests due to improper request validation in GraphQL multiplex query handling. This issue has been remediated by GitLab in the specified fixed versions.
AI Analysis
Technical Summary
CVE-2026-19650 is a security vulnerability in GitLab Community and Enterprise Editions affecting versions from 18.2 up to but not including 18.11.11, 19.0 up to but not including 19.0.8, 19.1 up to but not including 19.1.6, and 19.2 up to but not including 19.2.4. The flaw involves improper validation of GraphQL multiplex queries, which under certain conditions could allow an unauthenticated attacker to execute mutations via GET requests. This could lead to unauthorized modification of data. The vulnerability is classified under CWE-352 (Cross-Site Request Forgery). The CVSS v3.1 base score is 7.1, indicating a high severity with network attack vector, low attack complexity, no privileges required, user interaction required, unchanged scope, no confidentiality impact, high integrity impact, and low availability impact.
Potential Impact
The vulnerability allows unauthenticated users to perform unauthorized mutations through specially crafted GET requests exploiting improper validation in GraphQL multiplex query handling. This can lead to integrity violations by modifying data without proper authorization. There is no confidentiality impact reported. The vulnerability does not require privileges but does require user interaction. Availability impact is low.
Mitigation Recommendations
GitLab has released official fixes for this vulnerability in versions 18.11.11, 19.0.8, 19.1.6, and 19.2.4. Users should upgrade affected GitLab CE/EE instances to these versions or later to remediate the issue. Since this is not a cloud service, remediation depends on user action to apply the patches. Patch status is confirmed by the vendor advisory embedded in the description.
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… (CVE-2026-19650)
Description
A vulnerability in GitLab CE/EE 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 allows an unauthenticated user to execute mutations via GET requests due to improper request validation in GraphQL multiplex query handling. This issue has been remediated by GitLab in the specified fixed versions.
CVSS v3.1
Score 7.1high
Affected software
pkg:github/gitlab-org/gitlabRun on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2026-19650 is a security vulnerability in GitLab Community and Enterprise Editions affecting versions from 18.2 up to but not including 18.11.11, 19.0 up to but not including 19.0.8, 19.1 up to but not including 19.1.6, and 19.2 up to but not including 19.2.4. The flaw involves improper validation of GraphQL multiplex queries, which under certain conditions could allow an unauthenticated attacker to execute mutations via GET requests. This could lead to unauthorized modification of data. The vulnerability is classified under CWE-352 (Cross-Site Request Forgery). The CVSS v3.1 base score is 7.1, indicating a high severity with network attack vector, low attack complexity, no privileges required, user interaction required, unchanged scope, no confidentiality impact, high integrity impact, and low availability impact.
Potential Impact
The vulnerability allows unauthenticated users to perform unauthorized mutations through specially crafted GET requests exploiting improper validation in GraphQL multiplex query handling. This can lead to integrity violations by modifying data without proper authorization. There is no confidentiality impact reported. The vulnerability does not require privileges but does require user interaction. Availability impact is low.
Mitigation Recommendations
GitLab has released official fixes for this vulnerability in versions 18.11.11, 19.0.8, 19.1.6, and 19.2.4. Users should upgrade affected GitLab CE/EE instances to these versions or later to remediate the issue. Since this is not a cloud service, remediation depends on user action to apply the patches. Patch status is confirmed by the vendor advisory embedded in the description.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-78mw-f4q2-924q
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-19650"]
- Ecosystems
- []
- Database Specific Severity
- HIGH
- Cvss Version
- 3.1
Threat ID: 6a838c37bf8831d539b4b377
Added to database: 08/17/2026, 22:33:27 UTC
Last enriched: 08/17/2026, 23:11:07 UTC
Last updated: 08/18/2026, 01:29:28 UTC
Views: 21
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.