GitLab is a widely used DevOps platform; this flaw lets attackers poison repo cache to trigger CI with attacker content and expose protected env vars, risking code execution and secret leakage across organizations.
CVE-2026-14814
GitLab cache poisoning lets attackers trigger CI and expose protected variables.
Is CVE-2026-14814 being exploited?
Not confirmed. CVE-2026-14814 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.24% probability of exploitation in the next 30 days.
How severe is CVE-2026-14814?
CVE-2026-14814 is rated High with a CVSS score of 8.2. 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-14814?
Yes. A fix has been recorded for CVE-2026-14814. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-14814 affect?
CVE-2026-14814 affects GitLab CE/EE < 19.2.8, GitLab 19.3 < 19.3.5, GitLab 19.4 < 19.4.2. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-14814?
Upgrade GitLab to fixed versions and rotate CI secrets
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Poison raw repo cached responses to make targeted users' CI/CD run attacker-controlled content and expose protected environment variables.
Immediate action required
- affected< 19.2.8
- affected>= 19.3 and < 19.3.5
- affected>= 19.4 and < 19.4.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.