Security Digest · Vulnerability record

CVE-2026-110264: Integer Overflow or Wraparound in GitLab

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…

CVSS 10.0 Critical EPSS 0.5% · p42 Patch this week

Should you act?

Critical and remotely reachable

No known exploitation yet, but it is network-reachable without credentials. This signal is computed from CISA KEV, EPSS and CVSS data; it is not an editorial verdict.

  • No confirmed exploitation. It is not in CISA’s KEV catalog and CISA’s SSVC assessment records no known exploitation. That can change quickly after a public write-up; re-check if you are affected.
  • EPSS 0.5%, percentile 42: FIRST’s model estimates a 0.5% chance of exploitation activity in the next 30 days, higher than 42% of all scored CVEs (low). EPSS is a probability, not a verdict.
  • Remotely reachable with no login and no user interaction. If the vulnerable service is exposed to the internet, prioritize it.
  • Editorial verdict: Patch this week. GitLab CVE-2026-110264: CVSS 10 RCE via Org-mode Files — Upgrade self-managed GitLab this week, and within a day or two if it is internet-facing with public projects or open sign-up; no attacks are known, but GitLab's own detection notes now spell out the root cause.

What it is

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.

Weakness type: CWE-190.

Product: GitLab GitLab · Assigned by: GitLab · Published: 2026-10-22

Affected and fixed versions

VendorProductAffected versions (per CVE record)
GitLabGitLab7.0 < 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

Severity scores

Scored byCVSSScoreVector
GitLab3.110 CriticalCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
  • Attack vector: network (remotely reachable)
  • Attack complexity: low
  • Privileges required: none (no login)
  • User interaction: none
  • Scope: changed (can affect other components)

CVSS measures how bad a flaw is if exploited, not how likely exploitation is. Read it next to the exploitation data below.

Exploitation and urgency

  • CISA KEV: not listed (no confirmed in-the-wild exploitation known to CISA).
  • CISA SSVC assessment: exploitation none, automatable yes, technical impact total.
  • FIRST EPSS (model of 2026-10-23): 0.51% probability of exploitation activity in the next 30 days; percentile 42.

Timeline

Sources and references

Original sources first. Version and fix details should always be confirmed against the vendor or project advisory.

Vulnerability records

  1. CVE.org record CVE-2026-110264 cve.org
  2. NVD entry CVE-2026-110264 nvd.nist.gov

Other references from the CVE record and advisory

  1. gitlab.com gitlab.com
  2. HackerOne Bug Bounty Report #4093475 hackerone.com
  3. docs.gitlab.com docs.gitlab.com

Today’s Security Digest