High

CSRF in GitLab GraphQL API allowing arbitrary mutations

IdentifiersCVE-2026-3857CWE-352· Cross-Site Request Forgery (CSRF)

CVE-2026-3857 is a cross-site request forgery vulnerability in GitLab CE/EE caused by insufficient CSRF protection in GraphQL functionality (described as 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 victim who is authenticated to GitLab to visit a malicious webpage, causing the victim's browser to submit arbitrary GraphQL mutation requests to the GitLab instance in the context of that authenticated session. As a result, attacker-chosen state-changing GraphQL operations may be executed as the victim user.

For your environment

Are you exposed to this one?

Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.

Start free trial

ANALYST BRIEF

Impact, mitigation & remediation

What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation allows an unauthenticated attacker to perform arbitrary GraphQL mutations as the victim user, inheriting that user's effective permissions within GitLab. Depending on the victim account's role and accessible resources, this can result in unauthorized modification of GitLab data and settings, exposure of sensitive information through mutation side effects, and integrity compromise of projects, groups, or account state. The provided CVSS vector indicates high confidentiality impact, high integrity impact, and no direct availability impact.

Mitigation

If you can’t patch tonight, do this now.

If immediate patching is not possible, reduce exposure by limiting user access to untrusted websites while authenticated to GitLab, enforcing browser and organizational controls that reduce CSRF risk, and restricting external reachability of GitLab to trusted networks or users where feasible. Additional compensating controls may include monitoring for unexpected GraphQL mutation activity performed by legitimate users and reducing session exposure, but these measures are temporary and do not replace upgrading to a fixed version.

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. Any affected version from 17.10 up to but excluding those patched releases should be considered vulnerable. Apply GitLab's vendor patches and standard patch-release guidance.

PUBLIC EXPLOITS

Exploits

No public exploits tracked yet. Mallory keeps watching.

VALID 0 / 0 TOTALView more in app

No public exploit code observed for this vulnerability.

EXPOSURE SURFACE

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.

VendorProductType

GitLabGitlabapplication

Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.

ACTIVITY FEED

Recent activity

11 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

11 SOURCESView more in app

cvefeed high severityNews

Mar 25, 2026

CVE-2026-3857 - Cross-Site Request Forgery (CSRF) in GitLab

A GitLab CE/EE vulnerability caused by insufficient CSRF protection that could allow an unauthenticated attacker to execute arbitrary GraphQL mutations as authenticated users.

What this page doesn’t show

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, which detections to deploy, and what to do tonight.

Start free trial

Exposure mapping

Query your assets running an affected version, and investigate the blast radius.

Threat actor evidence

Every observed campaign linking this CVE to a named adversary.

Associated malware

Malware families riding this exploit, with evidence and IOCs.

Detection signatures

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

Vendor-by-vendor mapping

Cross-references every affected SKU, including bundled OEM variants.

Social activity9