
Urgent security update
GitLab fixes CVSS 10 flaw that can allow unauthenticated server code execution
Self-managed GitLab CE and EE operators should check their exact version and move to the fixed release for their branch. GitLab.com is already patched.
Reporting cutoff: October 21, 2026, 5:33 p.m. EDT (21:33 UTC).
What the vulnerability does
GitLab describes CVE-2026-110264 as an integer overflow in the regular-expression compiler: compiling a specially crafted regular expression can, under certain conditions, allow unauthenticated arbitrary code execution on the server.[1] Its published CVSS v3.1 vector is CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H.[1]
The short release advisory leaves the phrase “under certain conditions” undefined. GitLab’s linked technical detection material adds that the affected path is the Org-mode renderer and says an attack needs no authentication and only one public project capable of holding the crafted .org content.[2][3] Treat that as the currently documented exposure predicate, not as proof that every reachable GitLab instance has been exploited.
Exact affected and fixed versions
The following branch-by-branch ranges reproduce GitLab’s October 21 advisory.[1]
| Installed branch | Affected releases | First fixed release named by GitLab |
|---|---|---|
| 7.0 through 18.11 | 7.0 and later, before 18.11.13 | 18.11.13 |
| 19.0 | Before 19.0.10 | 19.0.10 |
| 19.1 | Before 19.1.9 | 19.1.9 |
| 19.2 | Before 19.2.9 | 19.2.9 |
| 19.3 | Before 19.3.6 | 19.3.6 |
| 19.4 | Before 19.4.3 | 19.4.3 |
| 19.5 | Before 19.5.1 | 19.5.1 |
GitLab says the 18.11.13, 19.0.10, 19.1.9 and 19.2.9 fixes are exceptional backports in addition to its standard patch releases.[1] Operators on substantially older releases should follow GitLab’s supported upgrade-path and required-stop guidance.[5]
Hosted services and upgrade impact
GitLab.com is already running a patched version. GitLab Dedicated tenants on 19.3.5-internal0, 19.4.2-internal0, or later already include the fixes and do not need customer action for this advisory.[1]
The patch release includes database migrations. GitLab warns that single-node installations will have downtime while migrations complete; 19.3.6 and 19.4.3 include regular migrations, and 19.4.3 also includes post-deploy migrations.[1] Multi-node operators can use GitLab’s zero-downtime procedure only when its architecture and sequencing requirements are met, including load balancing, high-availability mechanisms, one-minor-release-at-a-time upgrades and post-deployment migrations.[6]
What is known about exploitation
GitLab published “Onigmo native worker crash” and “Org mode render error burst” detections for self-managed instances.[1] GitLab’s detection documentation says these are attempt or corroboration signals: a successful exploit can be quiet, and the absence of a crash does not clear an attempted or successful compromise.[2][3]
At the reporting cutoff, CVE-2026-110264 was not present in CISA’s Known Exploited Vulnerabilities catalog version 2026.10.21.[7] The CVE Program API returned CVE_RECORD_DNE, and NVD’s API returned zero records for the identifier.[8][9] Those are point-in-time catalog results, not proof that exploitation has never occurred or that no exploit exists.
What self-managed operators should do now
- Confirm the deployment and exact version. An authenticated user can find it under Help → Help; do not classify GitLab.com as a self-managed exposure.[4]
- Preserve evidence before disruptive work if compromise is suspected. Retain relevant Rails exception, Puma worker-error and Workhorse logs, plus suspicious payload files. GitLab’s linked rules identify the relevant Org-render timeout and Onigmo crash signals, while warning that neither a hit nor a miss is standalone proof.[2][3]
- Plan the upgrade rather than improvising it. GitLab’s pre-upgrade guidance calls for the correct upgrade path, health checks, a tested rollback plan, a backup that includes secrets and configuration, and a production-like test where available.[5]
- Install the fixed release for the branch. Account for the migration and downtime notes above; multi-node zero-downtime work must follow GitLab’s documented architecture and order.[1][6]
- Verify more than the version string. Re-run GitLab’s health checks, confirm database and background migrations completed, test sign-in and repository operations, and verify runners and registries used by the organization.[5]
Temporary containment guidance—not a vendor workaround: if an immediate update is impossible, reduce untrusted network reachability and restrict creation or rendering of public Org-mode content where business operations permit. This is defense in depth inferred from GitLab’s documented attack path; it does not replace the fixed release.[2][3]
What remains unknown
- The patch advisory does not spell out all trigger conditions or configuration dependencies beyond “under certain conditions.”[1]
- No reviewed authoritative source established successful in-the-wild exploitation by the reporting cutoff; KEV absence and vendor silence must not be read as proof of no exploitation.[1][7]
- The CVE Program and NVD records were not yet available through their APIs at the cutoff, so GitLab’s advisory is the controlling source for the score, description and version matrix.[8][9]
Sources
- GitLab Critical Patch Release: 19.5.1 and backports — published October 21, 2026; retrieved October 21, 2026. Back to top
- GitLab Security OSS: Onigmo native worker crash detection — dated October 20, 2026; retrieved October 21, 2026.
- GitLab Security OSS: Org mode render error burst detection — dated October 20, 2026; retrieved October 21, 2026.
- GitLab Docs: Find the GitLab version — retrieved October 21, 2026.
- GitLab Docs: Before you upgrade — retrieved October 21, 2026.
- GitLab Docs: Upgrade a multi-node instance with zero downtime — retrieved October 21, 2026.
- CISA Known Exploited Vulnerabilities catalog — catalog version 2026.10.21, released October 21, 2026; retrieved October 21, 2026.
- CVE Program API lookup for CVE-2026-110264 — no record at retrieval on October 21, 2026.
- NVD API lookup for CVE-2026-110264 — zero results at retrieval on October 21, 2026.
