CVE-2026-122045
GitLab Duo settings could be configured for ineligible groups
GitLab · GitLab Duo group settings
First documented disclosure · Review checkpoint
Summary
Users could configure AI features for groups lacking an eligible license.
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
Group feature configuration lacked a required authorization check.
Conditions required
An authenticated user invokes the affected group-setting operation.
Potential impact
The group’s licensed AI-feature configuration boundary can be bypassed.
Affected versions and configurations
16.10 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 feature eligibility on configuration writes.
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 group settings original advisory
Primary source ·
- CERT-FR GitLab advisory
Primary source ·
- ENISA EUVD-2026-126845
Primary source ·