VulnerabilityPublished 27 Mar 2026Updated 10 Sep 2026

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

Affects gitlabSource GCVE Database

Not known to be exploited · fixed in 18.10.1 : patch gitlab soon.

Data as of 26 Oct 2026, 09:16 UTC

Severity

High

Rated by Threat Radar · No CVSS score from NVD or the CNA

EPSS: 0.2% chance of exploitation in 30 days – higher than 11% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 18.10.1, 18.9.3, 18.8.7

Exploitation evidence

Disclosed: evidence found.
CVE published 27 Mar 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade gitlab to 18.10.1, 18.9.3 or 18.8.7.

Affected software

Product	Affected	Fixed in
Bitnamigitlab`pkg:bitnami/gitlab`Other threats	Affected >=17.10.0 <18.8.7 >=18.9.0 <18.9.3 >=18.10.0 <18.10.1	Fixed in 18.8.7 18.9.3 18.10.1

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade GitLab CE/EE to versions 18.8.7, 18.9.3, or 18.10.1 or later to apply the official fix. Since a patch is available, applying the update is the recommended remediation.

Description

A Cross-Site Request Forgery (CSRF) vulnerability in GitLab CE/EE allows unauthenticated users to execute arbitrary GraphQL mutations on behalf of authenticated users. This issue affects GitLab versions from 17.10 up to but not including 18.8.7, 18.9 up to but not including 18.9.3, and 18.10 up to but not including 18.10.1. The vulnerability is due to insufficient CSRF protection. A patch is available that addresses this issue.

Impact

An unauthenticated attacker could exploit this vulnerability to execute arbitrary GraphQL mutations on behalf of authenticated users, potentially leading to unauthorized actions within GitLab. This could compromise the integrity and security of affected GitLab instances.

Summary

GitLab CE/EE versions >=17.10.0 <18.8.7, >=18.9.0 <18.9.3, and >=18.10.0 <18.10.1 contain a CSRF vulnerability that could allow an unauthenticated attacker to perform arbitrary GraphQL mutations as authenticated users. This occurs because of inadequate CSRF protections in the affected versions. The vendor has remediated the issue in versions 18.8.7, 18.9.3, and 18.10.1 respectively.

References

Community reviews

Loading reviews…