CVE-2026-103515BIT-GITLAB-2026-103515
Incorrect Authorization in GitLab
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 19.3.6, 19.4.3, 19.5.1
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
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.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- GitLab GitLab
From 19.2 · fixed in 19.3.6; From 19.4 · fixed in 19.4.3; From 19.5 · fixed in 19.5.1
- gitlabBitnami
From 19.2.0 · fixed in 19.3.6; From 19.4.0 · fixed in 19.4.3; From 19.5.0 · fixed in 19.5.1