Auth bypass in GitLab
CVE-2026-103515
GitLab has remediated an issue in GitLab EE affecting all versions from 19.2 before 19.3.6, 19.4 before 19.4.3, and 19.5 before 19.5.1 that, when an instance administrator locked a group's Duo availability, an authenticated user with group Owner permissions could have re-enabled AI-backed data egress to a third-party service for that group and its descendant projects, due to insufficient granularity of the admin-lock enforcement controls.
Vulnerability class: Broken Access Control
Published · last modified .
CVSS v3 metric
CVSS v3 base score 2.7 (Low). Vector: CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:L/A:N.
EPSS exploit prediction
No EPSS score from FIRST.org yet. New CVEs usually get one within a few days; no score means no signal yet, not low risk. How EPSS works.
Affected products
Weakness classification (CWE)
References
- gitlab.com/gitlab-org/gitlab/-/work_items/631564
- hackerone.com/reports/3871692 (technical-description, permissions-required, exploit)
- docs.gitlab.com/releases/patches/patch-release-gitlab-19-5-1-released/
Frequently asked questions
- What is CVE-2026-103515?
- CVE-2026-103515 is a low-severity vulnerability in GitLab, classified under Incorrect Authorization. CVSS score: 2.7/10. Published 2026-10-22.
- How severe is CVE-2026-103515?
- Low severity. CVSS v3 base score is 2.7 out of 10.