CVE-2026-19228
Auth user can cause AI usage to be attributed to another namespace in GitLab EE.
Is CVE-2026-19228 being exploited?
Not confirmed. CVE-2026-19228 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.23% probability of exploitation in the next 30 days.
How severe is CVE-2026-19228?
CVE-2026-19228 is rated High with a CVSS score of 8.5. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-19228?
Yes. A fix has been recorded for CVE-2026-19228. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-19228 affect?
CVE-2026-19228 affects GitLab EE 19.1 before 19.1.4, GitLab EE 19.2 before 19.2.2, Self-managed GitLab EE instances. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-19228?
Upgrade GitLab EE to 19.1.4 or 19.2.2+ immediately
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Authenticated attacker can spoof namespace identity in AI requests to misattribute usage, enabling billing fraud, audit tampering, and accountability/privacy compromise.
Patch when possible
- affected>= 19.1 and < 19.1.4
- affected>= 19.2 and < 19.2.2
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.