CVE-2025-11971VulnerabilityPublished 27 Oct 2025Updated 31 Oct 2025

GitLab Has Remediated an Issue

Affects gitlabSource GCVE Database

Compare

Not known to be exploited · CVSS 6.5 Medium · fixed in 18.3.5 : update gitlab when convenient.

Data as of 29 Oct 2026, 23:28 UTC

CVSS 3.1 base score

6.5Medium

How severe the flaw is on the 0–10 CVSS scale.

Patch: Available – fixed in 18.3.5

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

Attack Vector: Network
Attack Complexity: High
Privileges Required: Low
User Interaction: Required
Scope: Changed
Confidentiality: High
Integrity: Low
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: High: A successful attack depends on conditions beyond the attacker's control. That is, a successful attack cannot be accomplished at will, but requires the attacker to invest in some measurable amount of effort in preparation or execution against the vulnerable component before a successful attack can be expected. For example, a successful attack may require an attacker to: gather knowledge about the environment in which the vulnerable target/component exists; prepare the target environment to improve exploit reliability; or inject themselves into the logical network path between the target and the resource requested by the victim in order to read and/or modify network communications (e.g., a man in the middle attack).
Privileges Required: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
User Interaction: Required: Successful exploitation of this vulnerability requires a user to take some action before the vulnerability can be exploited.
Scope: Changed: An exploited vulnerability can affect resources beyond the security scope managed by the security authority of the vulnerable component. In this case, the vulnerable component and the impacted component are different and managed by different security authorities.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 27 Oct 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: 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 29 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.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), 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

Affected software

Product	Affected	Fixed in
Ubuntu 16.04 LTSgitlab`pkg:deb/ubuntu/gitlab?arch=source&distro=xenial`Other threats	Affected =8.4.3+dfsg-9 =8.4.3+dfsg-12 =8.5.8+dfsg-5	Fixed in–

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

AI-suggested

Upgrade GitLab EE to version 18.3.5, 18.4.3, 18.5.1, or later to remediate this vulnerability. Since fixed versions are available, applying the official patches is the recommended mitigation.

Description

A vulnerability in GitLab Enterprise Edition (EE) versions from 10.6 before 18.3.5, 18.4 before 18.4.3, and 18.5 before 18.5.1 could allow an authenticated attacker to trigger unauthorized pipeline executions by manipulating commits. This issue has been remediated in the specified fixed versions. The vulnerability has a CVSS 3.1 base score of 6.5, indicating a medium severity level.

Impact

An authenticated attacker with low privileges could exploit this vulnerability to trigger unauthorized pipeline executions, which could lead to unauthorized code execution or changes in the CI/CD process. The impact includes high confidentiality loss and low integrity loss, with no impact on availability as per the CVSS vector.

Summary

GitLab EE contained a vulnerability affecting all versions from 10.6 up to but not including 18.3.5, 18.4 up to but not including 18.4.3, and 18.5 up to but not including 18.5.1. The flaw allowed an authenticated attacker with low privileges to manipulate commits to trigger unauthorized pipeline executions, potentially impacting confidentiality and integrity. The issue has been fixed in versions 18.3.5, 18.4.3, and 18.5.1 respectively. No known exploits in the wild have been reported.

References

Community reviews

Loading reviews…