CVE-2026-103515VulnerabilityPublished 21 Oct 2026Updated 8 Nov 2026

Bundesamt für Sicherheit in der Informationstechnik Open Source · GitLab: Mehrere Schwachstellen

Affects Bundesamt für Sicherheit in der Informationstechnik Open SourceSource GCVE Database

Authoritative record:CVE-2026-103515· Low 2.7

Not known to be exploited · CVSS 2.7 Low · fixed in 19.5.1 : update Bundesamt für Sicherheit in der Informationstechnik Open Source when convenient.

Data as of 9 Nov 2026, 12:51 UTC

CVSS 3.1 base score

2.7Low

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

Thin evidence

One scorer or none

CVSS scores by source
CNA (GitLab)	CVSS 3.1	2.7

Patch: Available – fixed in 19.5.1, 19.4.3, 19.3.6

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

Attack Vector: Network
Attack Complexity: Low
Privileges Required: High
User Interaction: None
Scope: Unchanged
Confidentiality: None
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: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: High: The attacker is authorized with (i.e., requires) privileges that provide significant (e.g., administrative) control over the vulnerable component that could affect component-wide settings and files.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
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 21 Oct 2026
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 9 Nov 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.

bundesamt-f-r-sicherheit-in-de

What to do

Upgrade GitLab to 19.5.1, 19.4.3 or 19.3.6.

Affected software

Product	Affected	Fixed in
GitLabGitLab	Affected >=19.5 <19.5.1	Fixed in 19.5.1
GitLabGitLab	Affected >=19.4 <19.4.3	Fixed in 19.4.3
GitLabGitLab	Affected >=19.2 <19.3.6	Fixed in 19.3.6

AI-suggested

Users should upgrade GitLab to version 19.5.1 or later, where the vulnerabilities have been fixed. No additional mitigation steps are indicated by the vendor advisory.

Description

Multiple vulnerabilities have been identified in GitLab, a web application for software version control based on git. These issues affect versions prior to and including 19.5.1. A fix addressing these vulnerabilities is available in version 19.5.1.

References

Community reviews

Loading reviews…