Affects widely used GitLab CE/EE; allows CI/CD config tampering which can enable unauthorized job execution or supply-chain compromise across organizations.
CVE-2026-12436
Authenticated users can modify other users' GitLab CI/CD pipeline schedules.
Is CVE-2026-12436 being exploited?
Not confirmed. CVE-2026-12436 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.31% probability of exploitation in the next 30 days.
How severe is CVE-2026-12436?
CVE-2026-12436 is rated High with a CVSS score of 8.4. 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-12436?
Yes. A fix has been recorded for CVE-2026-12436. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-12436 affect?
CVE-2026-12436 affects GitLab CE/EE >=18.0 and <19.0.5, GitLab CE/EE 19.1 <19.1.3, GitLab CE/EE 19.2 <19.2.1. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-12436?
Upgrade to fixed GitLab versions and audit CI schedules/credentials.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Authenticated attacker can alter another user's CI/CD pipeline schedules, enabling unauthorized jobs, pipeline tampering, potential code injection or supply-chain compromise.
Patch when possible
- affected>= 18.0 and < 19.0.5
- affected>= 19.1 and < 19.1.3
- affected>= 19.2 and < 19.2.1
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.