Skip to content
major vulnerability· requires attention

GitLab is widely used enterprise software; unauthenticated mutation execution can lead to broad compromise and is newsworthy.

Web

CVE-2026-19650

9.4
Critical
EPSS 0.47%Patch availableAug 21, 2026

Unauthenticated GraphQL mutation execution via GET in GitLab

common questions

Is CVE-2026-19650 being exploited?

Not confirmed. CVE-2026-19650 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.47% probability of exploitation in the next 30 days.

How severe is CVE-2026-19650?

CVE-2026-19650 is rated Critical with a CVSS score of 9.4. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-19650?

Yes. A fix has been recorded for CVE-2026-19650. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-19650 affect?

CVE-2026-19650 affects GitLab CE/EE 18.2 before 18.11.11, GitLab 19.0 before 19.0.8, GitLab 19.1 before 19.1.6, GitLab 19.2 before 19.2.4. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-19650?

Upgrade to fixed GitLab versions immediately and restrict public GraphQL access until patched.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
GitLab CE/EE 18.2 before 18.11.11GitLab 19.0 before 19.0.8GitLab 19.1 before 19.1.6GitLab 19.2 before 19.2.4
impact

Unauthenticated attackers can invoke GraphQL mutations via GET to modify data, trigger actions, and potentially enable RCE or privilege escalation.

action required

Immediate action required

affected versions
GitLab GitLab
  • affected>= 18.2 and < 18.11.11
  • affected>= 19.0 and < 19.0.8
  • affected>= 19.1 and < 19.1.6
  • affected>= 19.2 and < 19.2.4

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free