Act nowVulnerabilities

GitLab fixes a maximum-severity flaw that needs no login: if you host GitLab yourself, update now

GitLab released an out-of-band patch on 21 Oct 2026 for CVE-2026-110264, rated 10 out of 10. It lets someone with no account run code on a self-managed server. GitLab.com is already fixed. Here is who must act.

Updated 30 Oct 2026: see what changed

How urgent

Act now

Who is affected

Anyone who runs their own GitLab server (self-managed, Community or Enterprise Edition) on a version older than 19.5.1, 19.4.3, 19.3.6, 19.2.9, 19.1.9, 19.0.10 or 18.11.13. GitLab.com and GitLab Dedicated are already patched

What to do

If you host GitLab yourself, update to the fixed version of your release line today and keep the server away from the open internet until you do. If you only use GitLab.com, no action is needed

Published 28 Oct 2026 · Sources last checked 30 Oct 2026No. 19 / 87

Updates, follow-ups and corrections

  1. Update · 30 Oct 2026. The other GitLab flaw, patched on 12 October, is now listed as exploited. On 29 Oct CISA added CVE-2026-97229 to its Known Exploited Vulnerabilities catalog, so if you stopped at the 12 October patch you are exposed to a flaw that is being used in attacks. Details and what to check in our new story.

We keep the original text. When something changes, when we follow a story, or when we get something wrong, we add a dated note here instead of editing silently.

What happened

On 21 October 2026 GitLab published an out-of-band critical patchPatch (security update) A fix released by the maker of a piece of software to close a flaw or a bug. Tap again to open the glossary release. It fixes CVE-2026-110264, an integer overflow in the part of GitLab that compiles regular expressions. GitLab says an unauthenticated user could potentially run code on the server. It rates the flaw 10.0 out of 10.

"Unauthenticated" means the person needs no account and no password. The release has 12 security fixes in total. One is critical and two are high.

Who is affected

Only people who run GitLab on their own server. According to GitLab, every self-managed version from 7.0 up to the fixed versions below is affected, in both the Community and Enterprise editions:

  • 19.5 before 19.5.1
  • 19.4 before 19.4.3
  • 19.3 before 19.3.6
  • 19.2 before 19.2.9
  • 19.1 before 19.1.9
  • 19.0 before 19.0.10
  • 18.11 before 18.11.13

GitLab.com is already patched, and so is GitLab Dedicated. If you only use GitLab.com to store your code, this does not need any action from you.

A detail that matters: the earlier patch of 12 October fixed a different flaw. If you only applied that one, you are still exposed to this one.

Is it being attacked?

GitLab's notice does not say it is being exploited, and we have not found a confirmed report of attacks. The company released two detections for self-managed servers, named "Onigmo native worker crash" and "Org mode render error burst", to help spot attempts. A flaw this severe, with no login needed, tends to be tried quickly once the details spread, so do not wait for a report of attacks.

Why it matters if you build with AI

Many small teams and AI-assisted projects host their own GitLab to keep code and CI secretsSecret (API key, token, password) Any piece of text that proves to a service that you are allowed in, such as an API key, a database password or an access token. Tap again to open the glossary in one place. A server like that often holds deploy keys, tokens and environment variables for every project. If someone takes over the server, they can read all of them. That is the same kind of damage we described in the Railway and LiteLLM stories this month.

What to do

  1. Find out if you host GitLab yourself. Ask whoever set it up. If your address is gitlab.com, you are fine.
  2. Update to the fixed version of your line. Use 19.5.1, 19.4.3, 19.3.6, 19.2.9, 19.1.9, 19.0.10 or 18.11.13. GitLab lists no workaround, so updating is the fix.
  3. If you cannot update today, limit access. Put the server behind a VPNVPN A private encrypted tunnel between your device and a network, so traffic does not travel in the open. Tap again to open the glossary or an allow list of IP addresses. This is our advice, not GitLab's, and it reduces exposure without fixing the flaw.
  4. If your version is older than those lines, plan an upgrade. GitLab does not list fixes for releases outside them.
  5. After updating, look at the logs. Check for the two detections above and for new users, tokens or deploy keys you do not recognise. If you find signs, rotate the tokens and keys stored in that server.

What we could not confirm

We read GitLab's official patch notice. We have not tested the flaw or the fix, and the notice gives no technical detail about how the flaw is triggered, which GitLab has chosen to withhold. We have not found reliable reports of attacks as of 28 October 2026, and that can change. For the exact upgrade steps for your version, use GitLab's documentation.

Watch the short video

The video loads from YouTube (privacy-enhanced mode) only when you press play.

Comments

No account needed. Add a nickname if you like, or leave it empty to comment anonymously. Comments are reviewed before they appear. Links are not allowed.

    We store your comment, your nickname and a scrambled form of your connection that we use only to limit spam. We do not store your IP address or set cookies. Cloudflare Turnstile checks that you are not a bot.

    Sources and verification

    We use primary sources first and say when we rely on a news report. Dates are the day we last checked each source.

    Spotted a mistake? Email [email protected] and we will correct it and note the change.

    Get the free runbooks

    One-page security checklists for founders who build with AI. You get a confirmation email first, then the runbooks.

    Send me the runbooks