Is CVE-2026-89078 exploited in the wild?

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

How severe is CVE-2026-89078?

Critical severity, with a CVSS score of 9.9, published 24 September 2026.

Which products and versions are affected?

GitLab Community Edition 19.2 before 19.2.7, 19.3 before 19.3.3, 19.4 before 19.4.1; GitLab Enterprise Edition 19.2 before 19.2.7, 19.3 before 19.3.3, 19.4 before 19.4.1.

Is there a fix for CVE-2026-89078?

A patch was published on 2026-09-23: Patched in GitLab CE/EE versions 19.2.7, 19.3.3, and 19.4.1 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-89078 attacked?

It is attacked over the network, in a web application.

Am I affected by CVE-2026-89078?

Check whether you run GitLab Community Edition or GitLab Enterprise Edition 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-89078: GitLab double free in regular expression parser

CVE-2026-89078 · Severity: critical · CVSS 9.9 · Published 2026-09-24

GitLab is a development platform that manages source code and CI/CD pipelines. An authenticated user can execute arbitrary code on the GitLab server by providing a specially crafted regular expression in CI/CD configuration. This allows an attacker with access to the platform to take complete control of the GitLab instance and access all hosted projects and data.

Technologies: GitLab Community Edition, GitLab Enterprise Edition. Vendors: GitLab.

Quick answers

Is CVE-2026-89078 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-89078 being exploited in the wild.
How severe is CVE-2026-89078?: Critical severity, with a CVSS score of 9.9, published 24 September 2026.
Which products and versions are affected?: GitLab Community Edition 19.2 before 19.2.7, 19.3 before 19.3.3, 19.4 before 19.4.1; GitLab Enterprise Edition 19.2 before 19.2.7, 19.3 before 19.3.3, 19.4 before 19.4.1.
Is there a fix for CVE-2026-89078?: A patch was published on 2026-09-23: Patched in GitLab CE/EE versions 19.2.7, 19.3.3, and 19.4.1 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-89078 attacked?: It is attacked over the network, in a web application.
Am I affected by CVE-2026-89078?: Check whether you run GitLab Community Edition or GitLab Enterprise Edition 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.

Technical details

A double free vulnerability in GitLab's regular expression parser allows authenticated users to execute arbitrary code when processing specially crafted regexes in CI/CD configuration files. The vulnerability is reachable via network from any authenticated user without user interaction required. An attacker gains code execution on the GitLab server with full system privileges; patches are available in versions 19.2.7, 19.3.3, and 19.4.1.

Affected products

GitLab GitLab Community Edition 19.2 before 19.2.7, 19.3 before 19.3.3, 19.4 before 19.4.1
GitLab GitLab Enterprise Edition 19.2 before 19.2.7, 19.3 before 19.3.3, 19.4 before 19.4.1

Timeline

2026-09-24: disclosed: Vulnerability disclosed in GitLab security release
2026-09-23: patched: Patched in GitLab CE/EE versions 19.2.7, 19.3.3, and 19.4.1

References

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