CVE-2025-11865VulnerabilityPublished 20 Nov 2025Updated 10 Sep 2026

CVE-2025-11865: GitLab · Incorrect Authorization

Affects gitlabSource GCVE Database

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

Data as of 26 Oct 2026, 07:57 UTC

Severity

Medium

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

EPSS: 0.2% chance of exploitation in 30 days – higher than 14% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 18.5.2, 18.4.4, 18.3.6

Exploitation evidence

Disclosed: evidence found.
CVE published 20 Nov 2025
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 2026-10-26.

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 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.5.2, 18.4.4 or 18.3.6.

Affected software

Product	Affected	Fixed in
Bitnamigitlab`pkg:bitnami/gitlab`Other threats	Affected >=18.1.0 <18.3.6 >=18.4.0 <18.4.4 >=18.5.0 <18.5.2	Fixed in 18.3.6 18.4.4 18.5.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 and should be applied by upgrading GitLab EE to version 18.3.6, 18.4.4, or 18.5.2 or later. Applying these updates will remediate the incorrect authorization vulnerability and prevent attackers from removing Duo flows of other users.

Description

GitLab EE versions 18.1 up to but not including 18.3.6, 18.4 up to but not including 18.4.4, and 18.5 up to but not including 18.5.2 contain an authorization vulnerability. This flaw could allow an attacker to remove Duo authentication flows of another user under certain conditions. A patch is available to address this issue.

Impact

An attacker exploiting this vulnerability could remove Duo authentication flows of other users, potentially reducing the security of those accounts by disabling their two-factor authentication. This could increase the risk of unauthorized access if the attacker subsequently attempts to compromise those accounts. There are no known exploits in the wild at this time.

Summary

CVE-2025-11865 is an incorrect authorization vulnerability in GitLab EE affecting versions >=18.1.0 <18.3.6, >=18.4.0 <18.4.4, and >=18.5.0 <18.5.2. The vulnerability permits an attacker, under specific circumstances, to remove Duo two-factor authentication flows belonging to other users. This could potentially weaken the targeted users' account security by disabling their multi-factor authentication setup. The issue has been fixed in versions 18.3.6, 18.4.4, and 18.5.2.

References

Community reviews

Loading reviews…