cve.bz

CVE-2026-129252 Authentication Bypass by Spoofing in GitLab

3.7 lowEPSS 0.1%

Low (3.7) in gitlab gitlab. EPSS 0.1% estimated probability of exploitation activity in the next 30 days.

On this page
GitLab has remediated an issue in GitLab CE/EE affecting all versions before 19.3.9, 19.4 before 19.4.8, and 19.5 before 19.5.6 that under certain conditions could have allowed an authenticated user with an unconfirmed email address to be automatically granted Group Owner-level membership during a group import operation, due to insufficient email verification enforcement in the member identity mapping process.

Severity

CVSS 3.1

3.7 low
CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:L/I:L/A:N
EPSS
0.1% estimated probability of exploitation activity in the next 30 days; 2nd percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2026-11-17. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-290 Authentication Bypass by Spoofing
OWASP Top 10
A07:2025 Authentication Failures
Published
Modified
Assigned by
GitLab (CNA)
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Ask an AI about this CVE

Show the promptExplain CVE-2026-129252 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-129252?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-129252?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-129252 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
GitLabbefore 19.3.9
GitLabfrom 19.4 before 19.4.8
GitLabfrom 19.5 before 19.5.6

Attack patterns (CAPEC)

  • CAPEC-21 Exploitation of Trusted Identifiers Likelihood: High · Severity: High
  • CAPEC-22 Exploiting Trust in Client Likelihood: High · Severity: High
  • CAPEC-59 Session Credential Falsification through Prediction Likelihood: High · Severity: High
  • CAPEC-60 Reusing Session IDs (aka Session Replay) Likelihood: High · Severity: High
  • CAPEC-94 Adversary in the Middle (AiTM) Likelihood: High · Severity: Very High
  • CAPEC-459 Creating a Rogue Certification Authority Certificate Likelihood: Medium · Severity: Very High
  • CAPEC-461 Web Services API Signature Forgery Leveraging Hash Function Extension Weakness Severity: High
  • CAPEC-473 Signature Spoof
  • CAPEC-476 Signature Spoofing by Misrepresentation Likelihood: Low · Severity: High
  • CAPEC-667 Bluetooth Impersonation AttackS (BIAS) Likelihood: Medium · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON