Skip to content
PiLabs security advisory Updated 17 November 2026
Critical 10.0 CVE-2026-97229 Known exploited

Unauthenticated code execution through regex validation flaw in GitLab CE and EE

Affected
GitLab Community Edition and Enterprise Edition
Affected versions
≥ 3.3.0, < 3.3.13; ≥ 3.4.0, < 3.4.12; ≥ 4.0.0, < 4.0.8; ≥ 19.2.0, < 19.2.8; ≥ 19.3.0, < 19.3.5; ≥ 19.4.0, < 19.4.2
Disclosed
Last updated
CVSS 3.1 vector
AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H

Written automatically on 17 November 2026 from the NVD and the CISA catalogue of known exploited vulnerabilities. The facts above come from those sources; check them before you act. Sources of this advisory

GitLab reports that CVE-2026-97229 in GitLab Community Edition and Enterprise Edition could let an unauthenticated user run arbitrary code on the server. CISA lists the vulnerability as exploited.

What is affected

GitLab reports a vulnerability in GitLab Community Edition and Enterprise Edition, tracked as CVE-2026-97229. The sources list these affected version ranges:

  • ≥ 3.3.0, < 3.3.13
  • ≥ 3.4.0, < 3.4.12
  • ≥ 4.0.0, < 4.0.8
  • ≥ 19.2.0, < 19.2.8
  • ≥ 19.3.0, < 19.3.5
  • ≥ 19.4.0, < 19.4.2

The issue was disclosed on 2026-10-13. The weakness is classified as CWE-190, integer overflow or wraparound. If you run a self-managed GitLab instance, compare your version with these ranges and with the vendor advisory.

What the flaw allows

According to the description from the sources, the flaw is caused by insufficient regular expression validation. Under certain conditions, an unauthenticated user could execute arbitrary code on the GitLab server by supplying a specially crafted regular expression in a CI/CD configuration.

The CVSS 3.1 base score is 10, which is critical. The vector shows that the flaw can be reached over the network, needs no privileges and no user interaction, and has low attack complexity. It also shows a changed scope and a high impact on confidentiality, integrity and availability. In practical terms, a successful attack on an exposed server could give an outsider control over that server and the data it holds.

Exploitation

CISA lists this vulnerability in its Known Exploited Vulnerabilities catalogue and added it on 2026-10-29. CISA gives 2026-11-01 as the due date, which is its stated deadline for US federal agencies. CISA records its knowledge of use in ransomware campaigns as unknown.

CISA's required action is to apply mitigations in accordance with the vendor's instructions. It also points to its guidance on forensic triage. Pinet has not analysed or tested this vulnerability; this advisory summarises what the public sources report. You can read the catalogue on the CISA Known Exploited Vulnerabilities catalogue page.

What to do

Check whether you operate GitLab Community Edition or Enterprise Edition in any of the ranges above, including test and internal instances. The vendor advisory lists the fixed releases and explains how to apply them. Details on the record are also available in the NVD entry for CVE-2026-97229. Because CISA lists the flaw as exploited, treat the update as urgent and see the mitigation section for the steps the sources describe.

What to do

Follow the instructions in the GitLab patch release advisory, which lists the fixed releases, and update every affected instance. CISA's required action is to apply mitigations in accordance with vendor instructions and to evaluate the internet exposure of each asset. CISA also refers to its forensic triage requirements for exploited vulnerabilities. The sources name no separate workaround.

Sources

All vulnerabilities

Need to know whether these vulnerabilities affect you?

A consultant can check which of the affected products you run and what to fix first. For a wider review, ask for a security assessment.