Affects widely used GitLab CE/EE CI/CD; can enable unauthorized deployments across organizations and disrupt release pipelines.
CVE-2026-15423
Authenticated developer can run CI pipelines on protected branches without push rights.
Is CVE-2026-15423 being exploited?
Not confirmed. CVE-2026-15423 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.26% probability of exploitation in the next 30 days.
How severe is CVE-2026-15423?
CVE-2026-15423 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-15423?
Yes. A fix has been recorded for CVE-2026-15423. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-15423 affect?
CVE-2026-15423 affects GitLab CE/EE 19.0 < 19.0.6, GitLab CE/EE 19.1 < 19.1.4, GitLab CE/EE 19.2 < 19.2.2. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-15423?
Upgrade to fixed GitLab versions (19.0.6, 19.1.4, 19.2.2+) and limit developer permissions until patched.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Authenticated users with developer role can trigger CI/CD on protected branches, enabling unauthorized deployments or execution of pipeline code.
Immediate action required
- affected>= 19.0 and < 19.0.6
- 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.