CVE-2026-104902
GitLab Duo seat and usage data could cross group boundaries
GitLab · GitLab Duo administration
First documented disclosure · Review checkpoint
Summary
Duo seat assignments and usage data from other groups could be read.
Severity and exploitation evidence
Medium · 4.3/10 · CVSS 3.1. Severity source.
Exploitation not established: Malicious exploitation status remains unverified in the reviewed sources.
Technical severity is not a measure of observed attacks or of risk to your deployment. Attempts, demonstrations, and successful compromise retain the qualifications in the source.
How the weakness works
Authorization checks did not consistently enforce group boundaries.
Conditions required
An authenticated user can access the affected administration path.
Potential impact
Cross-group AI usage and seat-assignment data can be disclosed.
Affected versions and configurations
17.7 through versions before 19.3.9, 19.4 before 19.4.8, and 19.5 before 19.5.6.
Fix and mitigation status
19.3.9, 19.4.8 and 19.5.6.
Practical next steps
Upgrade to a corrected release in the applicable maintenance branch.
Operating lesson
Enforce tenant boundaries on AI subscription and usage data.
Evidence and limits
Original disclosure 2026-11-16. The CVE Program published this record 2026-11-17. CERT-FR’s November 17 GitLab bulletin also lists this identifier.
Sources
- GitLab CVE authority record
Primary source ·
- GitLab Duo administration original advisory
Primary source ·
- CERT-FR GitLab advisory
Primary source ·
- ENISA EUVD-2026-126863
Primary source ·