Is CVE-2026-14814 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-14814 being exploited in the wild.

How severe is CVE-2026-14814?

High severity, with a CVSS score of 8.2, published 13 October 2026.

Which products and versions are affected?

GitLab EE before 19.2.8, 19.3 before 19.3.5, 19.4 before 19.4.2; GitLab CE before 19.2.8, 19.3 before 19.3.5, 19.4 before 19.4.2.

Is there a fix for CVE-2026-14814?

Yes: fixed in GitLab CE/EE 19.2.8, 19.3.5, 19.4.2. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-14814 attacked?

It is attacked over the network.

Am I affected by CVE-2026-14814?

Check whether you run GitLab EE, GitLab or GitLab CE at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-14814: GitLab cache poisoning via improper repository reference validation

CVE-2026-14814 · Severity: high · CVSS 8.2 · Published 2026-10-13

GitLab is a platform that hosts code repositories and runs automated CI/CD pipelines. An attacker can poison cached responses for raw repository files, causing CI/CD pipelines to execute malicious code and potentially exposing sensitive environment variables used in deployments. This could lead to code injection, credential theft, and unauthorized access to protected infrastructure.

Technologies: GitLab EE, GitLab, GitLab CE. Vendors: GitLab.

Quick answers

Is CVE-2026-14814 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-14814 being exploited in the wild.
How severe is CVE-2026-14814?: High severity, with a CVSS score of 8.2, published 13 October 2026.
Which products and versions are affected?: GitLab EE before 19.2.8, 19.3 before 19.3.5, 19.4 before 19.4.2; GitLab CE before 19.2.8, 19.3 before 19.3.5, 19.4 before 19.4.2.
Is there a fix for CVE-2026-14814?: Yes: fixed in GitLab CE/EE 19.2.8, 19.3.5, 19.4.2. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-14814 attacked?: It is attacked over the network.
Am I affected by CVE-2026-14814?: Check whether you run GitLab EE, GitLab or GitLab CE at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

Fixed in: GitLab CE/EE 19.2.8, 19.3.5, 19.4.2

Technical details

A cache poisoning vulnerability in GitLab CE/EE allows an authenticated user to manipulate cached responses for raw repository files through improper validation of repository references. Under certain conditions, an attacker can inject specially crafted content that gets executed in CI/CD pipelines of targeted users, potentially exposing protected environment variables. The vulnerability requires user authentication and network access to a GitLab instance.

Affected products

GitLab CE before 19.2.8, 19.3 before 19.3.5, 19.4 before 19.4.2
GitLab EE before 19.2.8, 19.3 before 19.3.5, 19.4 before 19.4.2

Timeline

2026-10-13: disclosed
2026-10-12: patched

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.