CVE-2026-3857: GitLab CE/EE CSRF Vulnerability

CVE-2026-3857 Overview

GitLab has remediated a Cross-Site Request Forgery (CSRF) vulnerability in GitLab CE/EE affecting all versions from 17.10 before 18.8.7, 18.9 before 18.9.3, and 18.10 before 18.10.1. This security flaw could have allowed an unauthenticated user to execute arbitrary GraphQL mutations on behalf of authenticated users due to insufficient CSRF protection.

Critical Impact

Unauthenticated attackers can execute arbitrary GraphQL mutations on behalf of authenticated users, potentially leading to unauthorized data modification, account compromise, or privilege escalation within GitLab instances.

Affected Products

• GitLab CE/EE versions from 17.10 before 18.8.7
• GitLab CE/EE versions 18.9 before 18.9.3
• GitLab CE/EE versions 18.10 before 18.10.1

Discovery Timeline

• 2026-03-25 - CVE-2026-3857 published to NVD
• 2026-03-25 - GitLab releases security patch (versions 18.8.7, 18.9.3, 18.10.1)
• 2026-03-26 - Last updated in NVD database

Technical Details for CVE-2026-3857

Vulnerability Analysis

This vulnerability is classified as CWE-352 (Cross-Site Request Forgery). The flaw exists in GitLab's GraphQL API implementation, where insufficient CSRF protection mechanisms allow malicious websites to forge requests that execute GraphQL mutations in the context of an authenticated user's session.

When a victim with an active GitLab session visits an attacker-controlled webpage, the malicious site can craft and submit GraphQL mutation requests to the victim's GitLab instance. Because the browser automatically includes session cookies with these requests, and the GraphQL endpoint lacks proper CSRF token validation, these forged requests are processed as legitimate actions performed by the authenticated user.

The vulnerability is particularly concerning because GraphQL mutations can perform sensitive operations including modifying repository settings, updating user profiles, managing access controls, and manipulating CI/CD configurations.

Root Cause

The root cause of this vulnerability lies in the insufficient implementation of CSRF protection for the GraphQL API endpoint. Specifically, the GraphQL mutation handlers did not properly validate CSRF tokens or implement origin-based request validation, allowing cross-origin requests to be processed without verification that they originated from legitimate GitLab pages.

Attack Vector

The attack requires user interaction in the form of visiting a malicious website while authenticated to a vulnerable GitLab instance. An attacker would host a webpage containing crafted JavaScript that automatically submits GraphQL mutation requests to the target GitLab server. The attack is network-based and does not require any privileges on the target system.

The attacker could embed the malicious payload in various delivery mechanisms including phishing emails, forum posts, or compromised legitimate websites. Upon successful exploitation, the attacker can perform any GraphQL mutation operation available to the victim's permission level.

Detection Methods for CVE-2026-3857

Indicators of Compromise

• Unexpected GraphQL mutation operations in GitLab logs originating from external referrers
• Repository or project settings modified without corresponding user-initiated activity in the UI
• User account modifications or permission changes with suspicious timing correlating to external link visits
• Access logs showing GraphQL API requests with external Referer headers

Detection Strategies

• Monitor GitLab production logs for GraphQL mutations with suspicious or missing CSRF tokens
• Implement correlation rules to detect GraphQL operations immediately following navigation from external domains
• Review audit logs for sensitive mutations (permission changes, repository modifications) and correlate with user activity patterns
• Deploy web application firewall rules to detect and alert on cross-origin GraphQL requests

Monitoring Recommendations

• Enable detailed request logging for the GitLab GraphQL API endpoint
• Configure SIEM alerts for high-volume or anomalous GraphQL mutation patterns
• Implement user behavior analytics to detect actions inconsistent with normal user activity
• Regularly audit GitLab configuration changes and correlate with authenticated user sessions

How to Mitigate CVE-2026-3857

Immediate Actions Required

• Upgrade GitLab CE/EE to patched versions: 18.8.7, 18.9.3, or 18.10.1 immediately
• Review audit logs for suspicious GraphQL mutations that may indicate prior exploitation
• Verify integrity of critical repository settings, user permissions, and CI/CD configurations
• Educate users about the risks of clicking untrusted links while authenticated to GitLab

Patch Information

GitLab has released patched versions addressing this vulnerability. Organizations should upgrade to:

• GitLab 18.8.7 for the 18.8.x branch
• GitLab 18.9.3 for the 18.9.x branch
• GitLab 18.10.1 for the 18.10.x branch

Detailed patch information is available in the GitLab Patch Release Notes. Additional technical details can be found in GitLab Work Item #592828 and the HackerOne Security Report #3584382.

Workarounds

• Implement strict Content Security Policy (CSP) headers to restrict cross-origin requests to the GitLab instance
• Configure web application firewall rules to block GraphQL requests with external referrers
• Advise users to use dedicated browser profiles for GitLab access and avoid browsing untrusted sites in the same session
• Consider implementing network-level restrictions to limit GraphQL API access to trusted origins until patching is complete