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...
Low CVSS 2.7
- CVE id
- CVE-2026-103515
- Published
- Last modified
Affected packages
| Package | Affected versions | Fixed in |
|---|---|---|
| GitLab EE Runtimes and servers |
>= 19.2.0, < 19.3.6 >= 19.4.0, < 19.4.3 |
19.3.6, 19.4.3 |
How to fix it
Upgrade GitLab EE to the fixed release of the line you run: 19.3.6, 19.4.3.
gitlab-rake gitlab:env:info
- Upgrade your self-managed GitLab EE (the gitlab/gitlab-ee image tag or the gitlab-ee package) to the patched release of your series.
A free AIssue account reads the runtime versions your repositories pin (version files, Dockerfiles, build files) and tells you when one is affected.
Details
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.
References
Am I affected?
Upload or paste your lockfile. We check every package version in it against OSV.dev, this advisory included, and email you the vulnerable ones with the version that fixes them. Free, and no account needed.
About this data
Source: National Vulnerability Database (NVD) (public domain). Severity comes from the advisory's own rating when it has one, else from its CVSS score.