CVE-2026-122226
GitLab Duo could retain access after a failed group-rule update
GitLab · GitLab Duo access controls
First documented disclosure · Review checkpoint
Summary
A failed policy update could leave restricted AI features accessible.
Severity and exploitation evidence
Low · 2.2/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
Error handling did not consistently restore group-based access restrictions.
Conditions required
An authenticated user encounters the affected access-rule update behavior.
Potential impact
Group-restricted Duo features can remain accessible.
Affected versions and configurations
18.8 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
Keep authorization policy consistent when an update fails.
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 access controls original advisory
Primary source ·
- CERT-FR GitLab advisory
Primary source ·
- ENISA EUVD-2026-126844
Primary source ·