What is the CVSS score of CVE-2026-3857?

CVE-2026-3857 has a CVSS 3.1 base score of 8.1 (High). CVSS vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N. EPSS exploitation probability: 0.0%.

Which versions of Gitlab are affected by CVE-2026-3857?

A critical vulnerability in GitLab allows attackers to hijack authenticated user accounts and perform unauthorized actions through forged requests, affecting all organizations using GitLab versions…. A patch is available.

Is there a public PoC exploit available for CVE-2026-3857?

Yes, a public proof-of-concept exploit is available for CVE-2026-3857. Prioritise patching immediately. EPSS: 0.0%.

How to fix or mitigate CVE-2026-3857?

Within 24 hours: Inventory all GitLab instances and confirm version numbers; disable GraphQL API access if not business-critical; enable detailed audit logging. Within 7 days: Implement WAF rules to block suspicious GraphQL mutations and enforce CSRF token validation; conduct access review for recent GraphQL activity logs. Within 30 days: Upgrade to patched versions (18.8.7, 18.9.3, or 18.10.1+) during maintenance windows; perform security assessment of potentially compromised accounts.

Gitlab CVE-2026-3857

EUVD-2026-15935 HIGH

Cross-Site Request Forgery (CSRF) (CWE-352)

2026-03-25 GitLab

Gitlab CSRF

8.1

CVSS 3.1 · NVD

Severity by source

NVD PRIMARY

8.1 HIGH

AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

Required

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

None

Lifecycle Timeline

Patch released

Mar 31, 2026 - 21:13 nvd

Patch available

PoC Detected

Mar 30, 2026 - 15:19 vuln.today

Public exploit code

EUVD ID Assigned

Mar 25, 2026 - 16:47 euvd

EUVD-2026-15935

Analysis Generated

Mar 25, 2026 - 16:47 vuln.today

CVE Published

Mar 25, 2026 - 16:33 nvd

HIGH 8.1

DescriptionCVE.org

GitLab has remediated an issue 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 that could have allowed an unauthenticated user to execute arbitrary GraphQL mutations on behalf of authenticated users due to insufficient CSRF protection.

AnalysisAI

A Cross-Site Request Forgery (CSRF) vulnerability in GitLab Community Edition and Enterprise Edition allows unauthenticated attackers to execute arbitrary GraphQL mutations on behalf of authenticated users without their consent. All versions from 17.10 before 18.8.7, versions 18.9 before 18.9.3, and versions 18.10 before 18.10.1 are affected. A public proof-of-concept exploit is available via HackerOne report 3584382, significantly increasing the risk of active exploitation.

Technical ContextAI

This vulnerability affects GitLab's GraphQL API implementation (cpe:2.3:a:gitlab:gitlab:*:*:*:*:*:*:*:*), which is used for programmatic interactions with GitLab repositories, CI/CD pipelines, and project management features. The root cause is classified as CWE-352 (Cross-Site Request Forgery), indicating insufficient validation of anti-CSRF tokens or missing SameSite cookie attributes on GraphQL mutation endpoints. GraphQL mutations in GitLab can perform state-changing operations such as modifying repository settings, creating merge requests, changing permissions, or triggering CI/CD pipelines. The lack of proper CSRF protection means that malicious websites can craft requests that authenticated users' browsers will automatically include valid session cookies with, allowing actions to be performed without the user's knowledge or consent.

RemediationAI

Immediately upgrade GitLab to one of the patched versions: 18.8.7 or later for the 18.8.x series, 18.9.3 or later for the 18.9.x series, or 18.10.1 or later for the 18.10.x series, as documented in the official security advisory at https://about.gitlab.com/releases/2026/03/25/patch-release-gitlab-18-10-1-released/. Until patching is completed, implement compensating controls such as educating users to avoid clicking untrusted links while authenticated to GitLab, deploying Content Security Policy headers to restrict cross-origin requests, and monitoring GraphQL mutation logs for suspicious patterns or unexpected sources. Consider implementing additional authentication requirements for sensitive GraphQL operations if your GitLab deployment supports custom authentication hooks. Review recent GraphQL mutation activity for signs of unauthorized actions that may have occurred prior to patching.