Skip to main content
VulnerabilityPublished

CVE-2026-129252: GitLab · Authentication Bypass by Spoofing

Affects GitLabSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 3.7 Low · fixed in 19.5.6 : update GitLab when convenient.

Data as of 17 Nov 2026, 04:35 UTC

CVSS 3.1 base score
3.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.13.7
Patch
Available – fixed in 19.5.6, 19.4.8, 19.3.9
CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:L/I:L/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 17 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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 16 Nov 2026.

What to do

Upgrade GitLab to 19.5.6, 19.4.8 or 19.3.9.

Affected software

ProductAffectedFixed in
GitLabGitLabAffected
  • >=19.5 <19.5.6
Fixed in
  • 19.5.6
GitLabGitLabAffected
  • >=19.4 <19.4.8
Fixed in
  • 19.4.8
GitLabGitLabAffected
  • <19.3.9
Fixed in
  • 19.3.9

CPE configurations (1)

  • cpe:2.3:a:gitlab:gitlab:*:*:*:*:*:*:*:*

AI-suggested

Upgrade GitLab CE/EE to versions 19.3.9, 19.4.8, or 19.5.6 or later where this vulnerability is fixed. No other mitigation is indicated by the vendor advisory.

Description

A vulnerability in GitLab CE/EE versions before 19.3.9, 19.4 before 19.4.8, and 19.5 before 19.5.6 could allow an authenticated user with an unconfirmed email address to gain Group Owner-level membership during a group import. This occurs due to insufficient enforcement of email verification in the member identity mapping process. The issue has been fixed in versions 19.3.9, 19.4.8, and 19.5.6.

References

Community reviews

Loading reviews…