No attacks reportedCVE published · 22 Oct 2026
GitLab
CVE-2026-110264 Severity · Critical
CVSS 10.0
Affected
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

CVE alert · Business web apps

CVE-2026-110264: A crafted Org-mode file lets anyone run code on a self-managed GitLab server

An attacker with no account can run code on a self-managed GitLab server through a crafted .org file in a public project, then steal build secrets and tokens. Versions from 7.0 up to each branch's fixed release are affected. Update to that release today.

Check your systems with your AI agent

Paste this prompt into an AI agent that can run commands on your machines. It only reads versions and settings, asks before using administrator rights, and ends with a report.

Check whether my systems are affected by CVE-2026-110264 in GitLab, then write me a report.

Read the alert first: https://securityaudit.ae/cve/cve-2026-110264-gitlab/

What the alert says (facts checked 24 October 2026):
- Affected: 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
- Exploited: No attacks reported as of 24 October 2026

Rules:
- Read only. Do not install, update, restart, delete or change anything, and never run exploit or proof-of-concept code.
- Run only commands that read versions or settings. Ask me before any command that needs sudo or administrator rights.
- If you do not know which machines, containers, cloud accounts or sites are in scope, ask me for the list before you start.
- If a machine cannot be reached or a command fails, say so. Do not guess.

Steps:
1. Find where GitLab runs: servers, containers and their hosts, cloud services, sites.
2. On each one, read the installed version and the settings the alert names. The alert gives these commands:

    sudo gitlab-rake gitlab:env:info

    bundle exec rake gitlab:env:info RAILS_ENV=production

    curl --request GET --header "PRIVATE-TOKEN: <your_access_token>" --url "https://<your-gitlab-host>/api/v4/metadata"

    sudo docker exec -it <container> gitlab-rake gitlab:env:info

3. Compare each version with the affected and fixed versions above. When a vendor or a distribution ships its own fixed package, the alert names it.
4. Report: one line per machine or service with the version found, Affected, Not affected or Unknown, and the evidence (the command and its output). Then the actions to take, in order, from the alert's "How to fix" section, and what you could not check.

Key facts

FactDetail
ProductGitLab Community Edition and Enterprise Edition (self-managed DevOps platform)
Affected versions7.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 in18.11.13, 19.0.10, 19.1.9, 19.2.9, 19.3.6, 19.4.3, 19.5.1 or later
Severity10.0 Critical (CVSS 3.1, GitLab)
Who can attackRemote attacker with no login; needs one public project that can hold the crafted .org file and that GitLab will render
ExploitedNo attacks reported as of 24 October 2026
CVE published22 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":

shell
sudo gitlab-rake gitlab:env:info

On a self-compiled install, run:

shell
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"):

shell
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":

shell
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:

shell
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:

shell
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.

Web app and API security test

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

Ask for a quote Book a call

Sources

  1. CVE-2026-110264 CVE Program (CNA: GitLab)
  2. CVE-2026-110264 Detail NIST NVD
  3. 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
  4. Detection: Org mode render error burst (CVE-2026-110264) GitLab Security
  5. Detection: Onigmo native worker crash GitLab Security
  6. Upgrade paths GitLab

The same update also fixes CVE-2026-15723, CVE-2026-112212.

More CVE alerts

All CVE alerts