Widely used GitLab CE/EE; CSRF weakness could allow unauthenticated users to perform GraphQL mutations, risking data/action abuse across orgs.
CVE-2026-3857
Unauthenticated GraphQL mutations due to CSRF flaw in GitLab CE/EE.
Is CVE-2026-3857 being exploited?
Not confirmed. CVE-2026-3857 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.17% probability of exploitation in the next 30 days.
How severe is CVE-2026-3857?
CVE-2026-3857 is rated High with a CVSS score of 8.1. 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-3857?
Yes. A fix has been recorded for CVE-2026-3857. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-3857 affect?
CVE-2026-3857 affects GitLab CE/EE, Versions <18.8.7, <18.9.3, <18.10.1. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-3857?
Upgrade to fixed GitLab versions; verify CSRF protection.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Unauthenticated attacker can trigger GraphQL mutations on behalf of authenticated users; risk data changes and unauthorized actions.
Patch when possible
- affected>= 17.10 and < 18.8.7
- affected>= 18.9 and < 18.9.3
- affected>= 18.10 and < 18.10.1
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.