Act nowVulnerabilities

CISA says the GitLab flaw patched on 12 October is being exploited: check your self-hosted server

On 29 Oct 2026 CISA added GitLab's maximum-severity flaw CVE-2026-97229 to its list of exploited vulnerabilities. GitLab fixed it on 12 Oct. A press report says the Alpine Linux project saw attacks on its own server. Who is affected and what to check.

Updated 3 Nov 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 19.2 before 19.2.8, 19.3 before 19.3.5 or 19.4 before 19.4.2, the versions GitLab lists for this flaw. GitLab.com and GitLab Dedicated are already patched

What to do

If you host GitLab yourself, update today to the fixed version of your line or newer, then look for signs of intrusion going back to 12 October. If you only use GitLab.com, no action is needed

Published 30 Oct 2026 · Sources last checked 3 Nov 2026No. 24 / 87

Updates, follow-ups and corrections

  1. Update · 3 Nov 2026. Press reports on 2 Nov, quoting scans by the Shadowserver Foundation, say more than 1,000 internet-exposed GitLab servers are still running code affected by CVE-2026-97229, three weeks after the 12 October patch. The count is of servers that look vulnerable, not of servers that were hacked. We could only read the headlines and summaries of those reports, not the full articles, so check your own server: if it is older than 19.4.2, 19.3.5 or 19.2.8, update today and review it for intrusion since 12 October.

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 29 October 2026 the US cyber agency CISA added CVE-2026-97229 to its Known Exploited VulnerabilitiesVulnerability A weakness in software, a setting or a process that an attacker could use to get in or do harm. Tap again to open the glossary list. That list is CISA's record of flaws it has evidence of being used in real attacks. The entry names GitLab Community and Enterprise Edition and describes the flaw as an integer overflow.

GitLab fixed this flaw on 12 October 2026 and rates it 10.0 out of 10. According to GitLab, a person with no account could run code on the server by sending a specially crafted regular expression in a CI/CD configuration. CI/CD is the automation that builds and ships your code.

This is a different flaw from the one in our story of 28 October (CVE-2026-110264, fixed on 21 October). The two sit in the same part of GitLab, and both are critical.

Who is affected

Only people who run GitLab on their own server. GitLab lists these versions for this flaw, in both editions:

  • 19.2 before 19.2.8
  • 19.3 before 19.3.5
  • 19.4 before 19.4.2

GitLab.com is already patched, and so is GitLab Dedicated. If you only use GitLab.com, you do not need to act.

What we know about the attacks

CISA's alert says the flaw is exploited but gives no details about who is doing it or how many servers were hit. According to heise online, the Alpine Linux project reported attacks on its own GitLab server on 20 and 21 October. heise says Alpine found no evidence that an attack succeeded, but rebuilt the server and reset all passwords to be safe. We have not read Alpine's own statement.

GitLab's notice says the company released six detections for self-managed servers to help spot attempts, among them a crash of the regular-expression engine and a burst of errors in the CI/CD check tool.

A detail to check: Ruby

heise also reports that the fix depends on the Ruby language that GitLab runs on being patched, and that Alpine's upgrade to a newer GitLab did not close the gap at first because its container image used a standard, unpatched Ruby. We could not confirm this in GitLab's notice, which lists regular-expression patchesPatch (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 for Ruby but gives no version numbers. If you run GitLab in a container or build your own image, ask whoever maintains it to confirm that the image is a current official one.

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. That server often holds deploy keys, tokens and environment variables for every project. If someone takes over the server, they can read all of them.

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 today to a fixed version: 19.4.2, 19.3.5 or 19.2.8 for this flaw, or the newer versions from our 28 October story (19.5.1, 19.4.3, 19.3.6, 19.2.9), which also cover the second flaw. If you run a container image, check that it is a current official one.
  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. Look for signs of intrusion back to 12 October. Check for the detections GitLab lists, and for new users, tokens, deploy keys or CI jobs you do not recognise.
  5. If you find signs, treat the server as compromised. Rotate every token, key and secret stored in it, as Alpine did with its passwords.

What we could not confirm

We read CISA's alert and GitLab's patch notice. We did not read Alpine Linux's own report, and the attack details and the Ruby point come only from heise. Neither CISA nor GitLab say who is attacking or how many servers were affected. We have not tested the flaw or the fix. For 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