CVE-2026-3857
8.1GitLab · GitLab CE/EE
GitLab CE/EE is vulnerable to a Cross-Site Request Forgery (CSRF) flaw allowing unauthenticated users to execute arbitrary GraphQL mutations on behalf of authenticated users.
Executive summary
A critical CSRF vulnerability in GitLab CE/EE allows unauthenticated attackers to perform unauthorized actions on behalf of authenticated users, potentially leading to full account compromise.
Vulnerability
This vulnerability, identified as CWE-352, involves insufficient CSRF protection within the GraphQL mutation interface. An unauthenticated attacker can trick an authenticated user into performing unintended actions by triggering unauthorized GraphQL mutations.
Business impact
The CVSS score of 8.1 indicates a high severity rating, reflecting the potential for significant unauthorized activity within the application. Successful exploitation could allow attackers to modify code, alter repository settings, or perform administrative tasks on behalf of a victim, resulting in severe data integrity loss and potential unauthorized access to proprietary intellectual property.
Remediation
Immediate Action: Upgrade all GitLab CE/EE instances to version 18.8.7, 18.9.3, or 18.10.1 immediately to apply the necessary security patches.
Proactive Monitoring: Review application access logs for suspicious GraphQL mutation requests or unusual user activity patterns that deviate from standard operational workflows.
Compensating Controls: Implement strict SameSite cookie policies and ensure that all GraphQL endpoints require valid CSRF tokens for state-changing operations to mitigate the risk until patching is completed.
Exploitation status
Public Exploit Available: Yes, a published proof-of-concept exists, as documented in the linked HackerOne security report.
Analyst recommendation
Given the ability for an attacker to bypass authentication protections and perform unauthorized mutations, this vulnerability poses a significant risk to the integrity of the development environment. Organizations should prioritize the deployment of the provided patches across all affected GitLab instances to neutralize this threat.
More GitLab CVEs
Sources
Originally found and disclosed by Thanks [ahacker1](https://hackerone.com/ahacker1) for reporting this vulnerability through our HackerOne bug bounty prog, per the CVE Program record.
- gitlab.com
- HackerOne Bug Bounty Report #3584382 Exploit / PoC
- about.gitlab.com