CVE-2026-125920
GitLab Duo usage analytics could be disrupted by authenticated input
GitLab · GitLab Duo usage analytics
First documented disclosure · Review checkpoint
Summary
An authenticated request could disrupt AI usage analytics.
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
The analytics operation accepted an improperly validated input quantity.
Conditions required
An authenticated user can reach the affected analytics functionality.
Potential impact
Availability of Duo usage analytics can be affected.
Affected versions and configurations
17.4 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
Bound the work permitted by analytics request parameters.
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 usage analytics original advisory
Primary source ·
- CERT-FR GitLab advisory
Primary source ·
- ENISA EUVD-2026-126842
Primary source ·