Critical GitLab CE and EE flaw allows unauthenticated remote code execution
GitLab has released CE and EE versions 19.4.2, 19.3.4 and 19.2.8, fixing 24 security issues including a critical remote code execution flaw, CVE-2026-97229. Any organisation running a self-managed GitLab instance is affected, and internet-facing servers are the most urgent.
What to do now
- Product
- GitLab Community Edition (CE) and Enterprise Edition (EE), self-managed
- Affected versions
- Self-managed GitLab CE/EE instances before 19.4.2, 19.3.4 and 19.2.8
- Fixed in
- 19.4.2, 19.3.4 and 19.2.8
- CVE
- CVE-2026-97229
On 12 October 2026, GitLab published security releases for GitLab Community Edition (CE) and Enterprise Edition (EE). Versions 19.4.2, 19.3.4 and 19.2.8 fix 24 security issues in total. CERT-EU reported the update the same day in its advisory 2026-016.
The most serious bug, CVE-2026-97229, sits in the regular expression compiler used by GitLab's CI/CD features. Regular expressions are not validated properly, which causes an integer overflow. A specially crafted expression placed in a CI/CD configuration can then run arbitrary code on the server. According to the advisory summary, an unauthenticated attacker could exploit it.
The release fixes several other significant flaws. CVE-2026-92883 is a cross-site scripting bug in syntax highlighting: an authenticated user can use a crafted repository to run JavaScript in other users' browsers. CVE-2026-16301 is an authorisation flaw that lets a developer run pipelines on protected branches without permission. The remaining 21 fixes include a cache poisoning issue that could expose protected CI/CD variables.
The advisory covers self-managed GitLab CE/EE instances running versions earlier than 19.4.2, 19.3.4 and 19.2.8. The source does not say whether the critical flaw is being exploited. It also describes no workaround, so upgrading is the only remedy it gives.
CERT-EU strongly recommends upgrading all self-managed instances as soon as possible, starting with those reachable from the internet.
What to do now
- Upgrade internet-facing GitLab CE/EE instances first to 19.4.2, 19.3.4 or 19.2.8, depending on the branch you run.
- Then apply the same upgrade to every other self-managed instance, including internal-only servers.
- As general good practice, review recent CI/CD configuration changes and server logs for unusual activity.
- As a precaution, consider rotating protected CI/CD variables and related secrets on any instance that stayed exposed without the fix.