English edition · cyberattaques.org in FrenchFrançais
VulnerabilityPatch available

Critical GitLab flaw allows unauthenticated remote code execution

On 21 October 2026, GitLab released fixes for several vulnerabilities, including CVE-2026-110264, a critical flaw that lets an unauthenticated user run arbitrary code on a GitLab server. Every organisation that self-hosts GitLab Community or Enterprise Edition is concerned, and CERT-EU urges them to update without delay.

What to do now Illustration photo (developer laptop code)
CVSS severity10.0Critical
EPSS probability1 %
ExploitationNot observed
PatchAvailable
Product
GitLab Community Edition and Enterprise Edition
Affected versions
7.0 up to before 18.11.13; 19.0 < 19.0.10; 19.1 < 19.1.9; 19.2 < 19.2.9; 19.3 < 19.3.6; 19.4 < 19.4.3; 19.5 < 19.5.1
Fixed in
18.11.13, 19.0.10, 19.1.9, 19.2.9, 19.3.6, 19.4.3, 19.5.1
CVE
CVE-2026-110264

CERT-EU published advisory 2026-019 on 22 October 2026, covering GitLab Community Edition and Enterprise Edition. It follows a security release that GitLab shipped the day before to fix several vulnerabilities.

The most serious of these is CVE-2026-110264, an integer overflow in the regular expression compiler. An attacker with no account can use it to execute arbitrary code on the affected GitLab server. A compromised instance may expose source code, stored secrets and CI/CD pipelines.

The flaw affects a very wide range of releases. Every version from 7.0 up to, but not including, 18.11.13 is vulnerable. So are the following branches until their fixed release: 19.0 before 19.0.10, 19.1 before 19.1.9, 19.2 before 19.2.9, 19.3 before 19.3.6, 19.4 before 19.4.3 and 19.5 before 19.5.1.

The same release also fixes two high-severity, five medium-severity and four low-severity issues. The advisory does not describe them, and it does not say whether the critical flaw is being exploited.

CERT-EU advises organisations to update as soon as possible, starting with internet-facing instances, and then to check for signs of compromise. GitLab has published two detection rules for this purpose. Their titles point to native worker crashes involving the Onigmo regular expression engine and to bursts of org-mode rendering errors.

Action plan

What to do now

  1. Upgrade each GitLab CE/EE instance to the fixed release for its branch: 18.11.13, 19.0.10, 19.1.9, 19.2.9, 19.3.6, 19.4.3 or 19.5.1.
  2. Patch internet-facing instances first, as CERT-EU recommends.
  3. Run GitLab's two published detection rules against your logs to look for exploitation attempts.
  4. If you find signs of exploitation, carry out a compromise assessment and, as general good practice, rotate the secrets and tokens stored on the server.

Sources