Skip to content
Thursday, October 22, 2026AboutContactRSS
Vulnerabilities

CVE-2026-110264: Flaw in GitLab Scores 10 on CVSS

A newly published critical vulnerability in GitLab carries a CVSS score of 10. Here is what is affected and how to respond.

CVE-2026-110264: Flaw in GitLab Scores 10 on CVSS
Illustration: Threat Times

Key points

  • CVE-2026-110264 affects GitLab.
  • CVSS 10 (Critical).
  • No exploitation confirmed yet.

GitLab is affected by CVE-2026-110264, a security flaw that the National Vulnerability Database rates 10 out of 10.

At a glance

CVE
CVE-2026-110264
Product
GitLab
CVSS
10 Critical
Weakness
CWE-190
Exploited
No known exploitation

What is the vulnerability?

The NVD entry states: An issue has been discovered in GitLab CE/EE affecting all versions from 7.0 before 18.11.13, 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 that, under certain conditions, could have allowed an unauthenticated user to execute arbitrary code on the GitLab server due to integer overflow when compiling a specially crafted regular expression.

Affected versions

VendorProductVersions
GitlabGitLabbefore 18.11.13, before 19.0.10, before 19.1.9, before 19.2.9

CVSS vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H.

Is it being exploited?

There is no public confirmation of exploitation at the time of publication. It does not appear in CISA's Known Exploited Vulnerabilities catalog. We will update this report if that changes.

What should you do?

  • Identify whether the affected product and versions run in your environment.
  • Apply the vendor update listed in the advisory as soon as it is available.
  • Limit network exposure of the affected service until it is patched.
  • Monitor the vendor advisory for updated guidance or exploitation reports.

What to do and how to stay safe: CVE-2026-110264

  • Vulnerability severity scores ignore your specific architecture and context.
  • Exploitability depends on network exposure and user behavior, not just code flaws.
  • Prioritization requires continuous asset inventory and threat intelligence alignment.

Risk-based vulnerability management focuses your limited resources on the flaws that actually threaten your business. Start by mapping your critical assets and checking for active exploits to prioritize your backlog.

Step-by-step guide: Risk-Based Vulnerability Management: Prioritize Fixes by Actual Danger

General security guidance from the Threat Times newsroom. It is not confirmed advice from the organisations named in this story.

Frequently asked questions

What is CVE-2026-110264?

CVE-2026-110264 is a CWE-190 vulnerability in GitLab.

How severe is CVE-2026-110264?

It has a CVSS score of 10 Critical.

Is CVE-2026-110264 being exploited?

There is no public confirmation of exploitation at the time of publication.

Sources

  1. NVD — CVE-2026-110264
  2. Reference
  3. Reference
  4. Reference
CVE-2026-110264GitLabCritical severity
Related articles