CVE-2026-103515
Incorrect Authorization in GitLab
Reported by gitlab · Published October 21, 2026
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.
Fixed versions
Upgrade to a fixed version or later. Language registries are listed first, then Linux distributions, then vendor products.
| Package | Ecosystem | Fixed in |
|---|---|---|
| GitLab | GitLab | 19.5.1, 19.4.3, 19.3.6 |
Risk scores
Affected products
| Vendor | Product | Versions |
|---|---|---|
| GitLab | GitLab | 19.2, 19.4, 19.5 |
| GitLab | GitLab | 19.2, 19.4, 19.5 |
Timeline
- Oct 21, 2026 CVE Published
- Oct 22, 2026 EPSS Score (3 in total, the first dated here)
- Oct 22, 2026 Coalition ESS Score
Query this with the API
The same record, from the CLI:
vulnetix vdb vuln CVE-2026-103515
vulnetix vdb fixes CVE-2026-103515Or with curl, using the org id and key from your account page:
curl -s -H "Authorization: ApiKey ${VULNETIX_ORG_ID}:${VULNETIX_API_KEY}" \
"https://api.vdb.vulnetix.com/v2/vuln/CVE-2026-103515/fixes/registry"The Community plan is free and allows 50 queries a day. Get a free API key · API quickstart
References
- HackerOne Bug Bounty Report #3871692 technical-descriptionexploitpermissions-required