Key facts
| Fact | Detail |
|---|---|
| Product | GitLab Community Edition and Enterprise Edition (self-managed DevOps platform) |
| Affected versions | 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; 19.5 before 19.5.1 |
| Fixed in | 18.11.13, 19.0.10, 19.1.9, 19.2.9, 19.3.6, 19.4.3, 19.5.1 or later |
| Severity | 10.0 Critical (CVSS 3.1, GitLab) |
| Who can attack | Remote attacker with no login; needs one public project that can hold the crafted .org file and that GitLab will render |
| Exploited | No attacks reported as of 24 October 2026 |
| CVE published | 22 October 2026 |
What an attacker can do
An attacker who needs no account can run commands on your GitLab server as the "git" user. The attacker can then read the secrets in gitlab-secrets.json, every CI/CD variable (settings and passwords your build pipelines use), runner tokens (keys that let build machines connect to GitLab) and access tokens. They can read and change every repository on the instance, and copy your source code and any customer data or credentials stored in it. With write access, they can also change code before your teams ship it. GitLab workers can crash during an attack campaign, which interrupts service for developers. GitLab rates the flaw 10.0, the highest score on CVSS, the standard 0 to 10 severity scale.
Who is affected
Self-managed GitLab Community Edition and Enterprise Edition are affected from version 7.0. The fixed releases are 18.11.13, 19.0.10, 19.1.9, 19.2.9, 19.3.6, 19.4.3 and 19.5.1. Below 18.11, follow GitLab's upgrade path through the required upgrade stops (x.2, x.5, x.8, x.11) to reach one of these releases.
The flaw affects every install type: the Linux package (Omnibus), source installs, the Helm chart and Docker. GitLab Dedicated tenants on 19.3.5-internal0, 19.4.2-internal0 or later need no action.
The attack goes through GitLab's viewer for Org-mode files (a plain-text notes format with the .org extension). The no-login attack needs one public project holding such a file.
The backport releases 18.11.13, 19.0.10, 19.1.9 and 19.2.9, which carry the fix over to older branches, fix only CVE-2026-110264. The release also fixes CVE-2026-15723 (8.2, account takeover when OmniAuth SAML and LDAP auto-linking are both on) and CVE-2026-112212 (7.5, OAuth/OIDC discovery cache poisoning), but only in 19.3.6, 19.4.3 and 19.5.1, so move to one of those.
How to check your version
In the web interface, any signed-in user can open the left sidebar and select Help > Help at the bottom. The version shows at the top of the page.
On a Linux package server, run this command and read "Version" under "GitLab information":
sudo gitlab-rake gitlab:env:info
On a self-compiled install, run:
bundle exec rake gitlab:env:info RAILS_ENV=production
Through the API, read the "version" field in the reply (for example "18.1.1-ee"):
curl --request GET --header "PRIVATE-TOKEN: <your_access_token>" --url "https://<your-gitlab-host>/api/v4/metadata"
On Docker, run this command and read "Version" under "GitLab information":
sudo docker exec -it <container> gitlab-rake gitlab:env:info
The image tag only gives the real version when you pinned a version number; a floating tag such as latest shows none.
What to do now
Update GitLab today to your branch's fixed release. Until then, make public projects private.
Check /var/log/gitlab/gitlab-rails/exceptions_json.log and /var/log/gitlab/puma/puma_stderr.log for .org render timeouts and crashes of org-ruby, the library that displays .org files, or of Onigmo, the Ruby text-search engine it uses. On Docker, use the same paths inside the container; on source installs, look in /home/git/gitlab/log/; on the Helm chart, read the logs of the gitlab-webservice-* pods, container webservice.
Search each checkout for the payload:
rg -l --hidden --no-ignore --glob '**/*.org' '^\#\+(TODO|SEQ_TODO|TYP_TODO):.{500,}'
Then check every branch and tag too, because GitLab renders .org files on any branch or commit:
git grep -l -E '^#\+(TODO|SEQ_TODO|TYP_TODO):.{500,}' $(git for-each-ref --format='%(refname)' refs/heads refs/remotes refs/tags) -- '*.org'
An attack through the editor preview leaves no file in the repository.
Signs of code execution: unexpected child processes of Puma (GitLab's web server), new git-owned files in /tmp, outbound connections, and changed git crontabs (scheduled tasks) or SSH keys. If you find any, the server is compromised: rotate the gitlab-secrets.json secrets, CI/CD variables, runner tokens and access tokens.
If you find only signs of attempts, block the source IP. Make the project private or remove the payload commits. GitLab warns that a successful attack may not crash anything.
Get help
Updating closes this flaw. Flaws in your own code get no CVE and no update, and a test of your app is how they are found.
A penetration test of your web app and its API: who can see whose data, and what an attacker can change.
From AED 20,000, excl. 5% VAT
Sources
- CVE-2026-110264 CVE Program (CNA: GitLab)
- CVE-2026-110264 Detail NIST NVD
- GitLab Critical Patch Release: 19.5.1, 19.4.3, 19.3.6, 19.2.9, 19.1.9, 19.0.10, 18.11.13 GitLab
- Detection: Org mode render error burst (CVE-2026-110264) GitLab Security
- Detection: Onigmo native worker crash GitLab Security
- Upgrade paths GitLab
The same update also fixes CVE-2026-15723, CVE-2026-112212.