VulnerabilityPublished 24 May 2024Updated 10 Sep 2026

CVE-2024-4597: GitLab · Cross-Site Request Forgery (CSRF)

Affects gitlabSource GCVE Database

Not known to be exploited · fixed in 16.11.2 : update gitlab when convenient.

Data as of 26 Oct 2026, 10:12 UTC

Severity

Medium

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

EPSS: 0.3% chance of exploitation in 30 days – higher than 23% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 16.11.2, 16.10.5, 16.9.7

Exploitation evidence

Disclosed: evidence found.
CVE published 24 May 2024
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 16.11.2, 16.10.5 or 16.9.7.

Affected software

Product	Affected	Fixed in
Bitnamigitlab`pkg:bitnami/gitlab`Other threats	Affected >=16.7.0 <16.9.7 >=16.10.0 <16.10.5 >=16.11.0 <16.11.2	Fixed in 16.9.7 16.10.5 16.11.2

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

AI-suggested

A patch is available for this vulnerability. Users should upgrade affected GitLab EE versions to 16.9.7 or later for the 16.7 branch, 16.10.5 or later for the 16.10 branch, and 16.11.2 or later for the 16.11 branch to remediate this issue. Applying these updates will prevent exploitation of the CSRF vulnerability.

Description

A Cross-Site Request Forgery (CSRF) vulnerability exists in GitLab Enterprise Edition that affects certain versions from 16.7 up to but not including 16.9.7, 16.10 up to but not including 16.10.5, and 16.11 up to but not including 16.11.2. This flaw allows an attacker to force a user with an active SAML session to approve a merge request without their consent.

Impact

An attacker may cause a user with an active SAML session to unknowingly approve a merge request, which could lead to unauthorized code changes being merged. This undermines the integrity of the code review and approval process within affected GitLab instances.

Summary

CVE-2024-4597 is a CSRF vulnerability in GitLab EE that impacts versions >=16.7.0 <16.9.7, >=16.10.0 <16.10.5, and >=16.11.0 <16.11.2. An attacker can exploit this issue to coerce a user authenticated via SAML into approving a merge request, potentially bypassing intended user interaction and authorization controls. This vulnerability requires the victim to have an active SAML session, and the attack leverages CSRF techniques to perform unauthorized actions.

References

Community reviews

Loading reviews…