CVE-2026-110264
CVE-2026-110264 is a critical-severity vulnerability in GitLab (CVSS 3.1 base score 10.0), classified as CWE-190 (Integer Overflow or Wraparound). It is not in the CISA Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment rates its exploitation as none. As of 2026-11-22, EPSS estimates a 54.0% probability of exploitation in the next 30 days, in the 99th percentile of scored CVEs.
Updated
- CVSS 3.1
- 10.0 CRITICAL
- EPSS
- 54.0% (99th pct)
- CISA KEV
- Not listed
- Published
- 2026-10-22
- Weakness
- CWE-190
Description
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.
Key Findings
as of 2026-11-22- Its current EPSS score (54.0%) is higher than that of 50% of CISA KEV entries.
Severity
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:HOpen in CVSS calculator Remediation Timeline
BOD 26-04, US federal agenciesIf CISA adds it to the KEV catalog: 3 days and forensic triage on a publicly exposed asset, 3 days and forensic triage on other assets.
Deadlines for US federal civilian agencies under Table 1 of CISA BOD 26-04, from the CVE's KEV status (not listed) and CISA's SSVC values (automatable yes, technical impact total, 2026-10-21).
How the timeline is set
Table 1 of CISA's Binding Operational Directive 26-04 sets the time US federal civilian agencies have to remediate a vulnerability. It depends on four inputs: whether the asset is publicly exposed, whether the CVE is in the KEV catalog, whether an adversary can automate its exploitation, and whether exploitation gives partial or total control of the asset, which SSVC calls technical impact. CISA publishes the last three for every CVE through services such as its Vulnrichment program.
Days are calendar days. The clock starts at whichever comes first: CISA adds the CVE to the KEV catalog, or the agency identifies the vulnerability on an asset and reports it to its Continuous Diagnostics and Mitigation (CDM) dashboard. A publicly exposed asset is accessible to unauthenticated or untrusted entities via public networks, such as the internet. Forensic triage means assessing the asset to determine whether it has been compromised.
If CISA adds the CVE to the KEV catalog, the timeline shortens.
Affected Products
| Vendor | Product | Affected versions |
|---|---|---|
| GitLab | GitLab GitLab | 7.0 to <18.11.13 19.0 to <19.0.10 19.1 to <19.1.9 19.2 to <19.2.9 19.3 to <19.3.6 19.4 to <19.4.3 19.5 to <19.5.1 |
Solutions and Workarounds
from the CNA's CVE recordSolution
Upgrade to versions 18.11.13, 19.0.10, 19.1.9, 19.2.9, 19.3.6, 19.4.3, 19.5.1, or later.
References
4 linksRecord Details
- Published
- 2026-10-22
- Last updated
- 2026-10-30
- Assigner (CNA)
- GitLab
- Credited to
- Thanks [joaxcar](https://hackerone.com/joaxcar) for reporting this vulnerability through our HackerOne bug bounty program
More from GitLab
GitLab Server-Side Request Forgery (SSRF) Vulnerability
Improper Control of Generation of Code ('Code Injection') in GitLab
GitLab Community and Enterprise Editions Remote Code Execution Vulnerability
Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') in GitLab
CVE record data © The MITRE Corporation, used under the CVE Terms of Use. Exploited-in-the-wild data from the CISA Known Exploited Vulnerabilities catalog (CC0). Exploit prediction scores by FIRST EPSS (first.org/epss). Alert titles and links from CISA cybersecurity alerts. This site is not affiliated with or endorsed by MITRE, NVD, CISA, or FIRST.