CVE-2026-3857: CSRF in GitLab CE/EE GLQL API
- Vendor
- GitLab
CVE-2026-3857 is a cross-site request forgery vulnerability in GitLab Community Edition and Enterprise Edition caused by insufficient CSRF protection in the GLQL API. It affects all versions from 17.10 before 18.8.7, 18.9 before 18.9.3, and 18.10 before 18.10.1. A remote, unauthenticated attacker can induce a logged-in victim to visit a malicious webpage and thereby trigger arbitrary GraphQL mutation requests in the victim’s authenticated session. Because the requests are executed with the victim user’s existing privileges, the flaw can be used to perform state-changing actions through the GraphQL interface without the victim’s intent or consent.
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 allows unauthorized execution of arbitrary GraphQL mutations as the targeted authenticated user. This can result in unauthorized changes to application state, misuse of the victim’s account permissions, exposure or modification of data accessible through those mutations, and compromise of workflow integrity. The published CVSS v3.1 vector indicates high confidentiality and integrity impact, with no direct availability impact.
Mitigation
If you can’t patch tonight, do this now.
If immediate patching is not possible, reduce exposure by minimizing opportunities for authenticated users to be lured to attacker-controlled webpages, enforcing strong browser and session security practices, and limiting unnecessary access to sensitive GraphQL mutation capabilities until upgrades can be completed. These measures are only temporary risk reductions and do not remediate the underlying CSRF weakness.
Remediation
Patch, then assume compromise.
Upgrade GitLab CE/EE to a fixed release: 18.8.7 or later for the 18.8 series, 18.9.3 or later for the 18.9 series, or 18.10.1 or later for the 18.10 series. Self-managed deployments should apply the vendor patch releases as soon as possible. Upgrade planning should account for the vendor-noted database migrations, which may cause downtime on single-node deployments unless zero-downtime procedures are used where supported.
Exploits
No public exploits tracked yet. Mallory keeps watching.
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-3857 exploited in the wild?
- As of Sep 25, 2026, Mallory has no reports of CVE-2026-3857 being exploited in the wild. It is not listed in CISA KEV.
- Is there a public exploit for CVE-2026-3857?
- As of Sep 25, 2026, Mallory has found no public exploit for CVE-2026-3857.
- Is there a patch for CVE-2026-3857?
- Upgrade GitLab CE/EE to a fixed release: 18.8.7 or later for the 18.8 series, 18.9.3 or later for the 18.9 series, or 18.10.1 or later for the 18.10 series. Self-managed deployments should apply the vendor patch releases as soon as possible.
- What products are affected by CVE-2026-3857?
- Gitlab.
- How severe is CVE-2026-3857?
- CVE-2026-3857 has a CVSS v3.1 score of 8.8 (High) and an EPSS score of 0.22% (13th percentile) as of Sep 25, 2026.
Recent activity
13 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.