CERT-EU: Critical GitLab flaw CVE-2026-110264 allows unauthenticated code execution

CERT-EU reports a critical GitLab flaw, CVE-2026-110264 (CVSS 10), that lets an unauthenticated user run arbitrary code on the server. Patched versions are available; internet-facing instances should be updated first.

A software engineer seen from behind works at a dual-monitor desk in a Riyadh office in late afternoon light.

Key points

  • GitLab published a security advisory on 21 October 2026; CERT-EU issued its notice on 22 October 2026.
  • CVE-2026-110264 is an integer overflow in the regular expression compiler, rated CVSS 10.
  • An unauthenticated user could execute arbitrary code on the affected GitLab server.
  • Community and Enterprise Editions are affected across several version lines, fixed in 18.11.13, 19.0.10, 19.1.9, 19.2.9, 19.3.6, 19.4.3 and 19.5.1.
  • GitLab also fixed 2 high, 5 medium and 4 low severity issues and published two detection rules.

CERT-EU has published advisory 2026-019 about a critical vulnerability in GitLab Community and Enterprise Editions. It follows a GitLab security release of 21 October 2026 that fixed several issues.

What is affected

The flaw, CVE-2026-110264, is an integer overflow in the regular expression compiler. It carries a CVSS score of 10. An unauthenticated user could use it to execute arbitrary code on the GitLab server.

Affected versions are those from 7.0 before 18.11.13, and the 19.x lines before the following fixed releases:

  • 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
  • 19.5 before 19.5.1

The same GitLab release also fixed 2 high, 5 medium and 4 low severity vulnerabilities.

What CERT-EU recommends

CERT-EU advises updating affected assets as soon as possible, starting with those reachable from the internet. It also recommends running an assessment to find any assets that may already be compromised. GitLab has published two detection rules for exploitation attempts, which can support that assessment.

Because source code, pipelines and credentials often sit on GitLab servers, institutions should treat this as an urgent patching and review task and record the outcome for governance purposes.

What to do now

  1. Inventory all GitLab Community and Enterprise instances and compare their versions with the fixed releases.
  2. Upgrade vulnerable instances to a fixed version, starting with internet-facing servers.
  3. Deploy the two GitLab detection rules in your monitoring tools and review past logs for exploitation attempts.
  4. Run a compromise assessment on exposed instances and rotate secrets and tokens stored in GitLab if compromise is suspected.
  5. Record the patching and assessment results under your vulnerability and change management processes.

How useful was this story?

Need help acting on this?

Our consultants can assess your exposure and map the change to your controls and evidence.

Talk to an expert

Regulatory updates in your inbox

SAMA, NCA and SDAIA changes and what they mean for your institution — once a month.

E-mails in

We confirm by e-mail; unsubscribe any time. Manage your subscription · Past issues

Schedule a Free Assessment