GitLab servers you run yourself: attackers are using a flaw fixed three weeks ago
2 November 2026Attackers are using a GitLab flaw to run their own code on servers firms host themselves. GitLab.com users don't need to do anything.

What happened
GitLab is a tool software teams use to store their code and run automatic builds. On 12/10/2026 GitLab fixed a flaw that lets an attacker run their own code on a GitLab server, using a booby trapped build settings file. GitLab rates it 10 out of 10 and says no login is needed. Security firm Rapid7 found the attacker first has to get that file into a project, which is easy on any server where strangers can sign up. On 29/10/2026 the US cyber agency CISA confirmed attackers are now using it. That server usually holds your source code and the passwords your builds use.
On 21/10/2026 GitLab fixed a second flaw of the same kind, also rated 10 out of 10. A server updated only for the first one is still open to the second.
Does this affect you
Only if your firm, your developer or your software supplier runs its own GitLab server. If you just use gitlab.com, GitLab says it is already patched and you don't need to do anything. GitLab also patched every GitLab Dedicated customer before it published the fix.
What to do
- Ask your developer or IT company: "Do we run our own GitLab, and what version is it?" Anyone signed in can see the version: in GitLab, select Help at the bottom of the left sidebar, and the version is at the top of that page.
- Update it this week to the newest release for its version. On 29/10/2026 GitLab's newest were 19.5.3, 19.4.5, 19.3.7, 19.2.10, 19.1.10, 19.0.11 and 18.11.14. Anything below 19.5.1, 19.4.3, 19.3.6, 19.2.9, 19.1.9, 19.0.10 or 18.11.13 is still open to one flaw or the other, and a server older than 18.11 has no fix in its own line, so it needs a bigger upgrade. GitLab says the update changes the database, so a GitLab that runs on a single server will be offline while it installs.
- If your GitLab was built from source or runs in a container image your team made, rather than GitLab's own packages, updating GitLab is not enough. GitLab says Ruby must also be 3.3.13, 3.4.12, 4.0.9 or later, because the fix is a patch to Ruby. The Alpine Linux project found its own upgrade had not closed the hole for exactly this reason.
- Until it is updated, stop strangers signing up and creating or writing to public projects. Rapid7 says this blocks the route it tested, but it doesn't fix the flaw.
- Because attacks have started, ask them to check the server for signs of a break in, using the six checks GitLab has published. Alpine Linux warns that a successful attack leaves no crash and no trace in the web logs, so if anything looks wrong, treat the server as broken into and change the passwords, keys and tokens stored in it.
Is it being attacked?
Yes. CISA added the first flaw to its list of flaws attackers are using on 29/10/2026, with a US federal deadline of 01/11/2026. Rapid7 has published code that proves the attack works. On 20 and 21/10/2026 an attacker using a newly registered account tried it on the Alpine Linux project's GitLab server, which had not yet been updated. Alpine says the attack came close to working and it found no evidence it succeeded, but it rebuilt the server from scratch to be safe. The second flaw is not on CISA's list (checked 04/11/2026).
Found by
A researcher called joaxcar reported both flaws through GitLab's HackerOne bug bounty, according to GitLab. Ruby's notice of 23/10/2026 names him as Johan Carlsson. Nothing says Ai was used. Tag: people.
For developers
- CVE-2026-97229: integer overflow in the CI/CD Regular Expression Compiler, unauthenticated arbitrary code execution via a crafted regex in CI/CD configuration. CVSS 3.1 10.0 (GitLab, AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H).
- Affected: GitLab CE/EE 19.2 before 19.2.8, 19.3 before 19.3.5, 19.4 before 19.4.2 (CVE record default status unaffected outside these ranges). GitLab.com and GitLab Dedicated already patched.
- CVE-2026-110264 (GitLab critical patch release, 21/10/2026): integer overflow when compiling a crafted regular expression, unauthenticated code execution, CVSS 3.1 10.0, also credited to joaxcar. Impacted: all versions from 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, and 19.5 before 19.5.1. GitLab backported this fix to 18.11.13, 19.0.10, 19.1.9 and 19.2.9 as well as its usual patch releases.
- Both are bugs in Onigmo, Ruby's regular expression engine. GitLab fixed them by patching the Ruby it ships, so the fix is only in GitLab's official Linux packages and container images. Self-compiled installs and custom images also need Ruby 3.3.13, 3.4.12 or 4.0.9 or later (GitLab's 19.5.1 notes, Ruby's notice of 23/10/2026). Ruby says only code that compiles a regular expression from attacker-controlled input is exposed, that
Regexp.timeoutdoes not protect against these bugs, and that limiting pattern length does not reliably help. - Precondition (Rapid7, 13/10/2026, updated 30/10/2026): the attacker must first commit a malicious
.gitlab-ci.ymland a repository path containing UTF-8 characters to a branch in a public project; open self-registration removes that constraint. Rapid7 reproduced code execution on an unpatched official GitLab CE image. Proof of concept: github.com/jburgess-r7/CVE-2026-97229-PoC. - GitLab published six threat detections for self-managed instances on the 19.4.2 release page: Onigmo native worker crash, Graphql cilint hostile regexp, ci regexp oversized non ascii path, ci regexp guard rejection, ci lint workhorse worker crash, ci lint scripted client error burst.
- Attack seen in the wild (Alpine Linux, 28/10/2026): a newly registered account sent crafted CI configurations to an instance on 19.3.4, crashing GitLab worker processes 8 times. Alpine's upgrade to 19.3.6 on 22/10/2026 did not fix it because its image used standard Ruby. Alpine notes a successful exploit "would leave no crash and no trace in the web logs".
- The 19.4.2 release also fixes more than 20 other security flaws, including CVE-2026-92883 (cross-site scripting, 8.7) and CVE-2026-16301 (8.5), and includes database migrations: single-node instances have downtime during the upgrade.
- CISA KEV: CVE-2026-97229 added 29/10/2026, due 01/11/2026, ransomware use Unknown (catalogue 2026.11.03, checked 04/11/2026). CISA notes other products may be affected by the same underlying Ruby/Onigmo issue and links Ruby's 23/10/2026 notice. CVE-2026-110264 is not on KEV.
- BleepingComputer (02/11/2026) quotes Shadowserver tracking over 1,000 instances still vulnerable to CVE-2026-97229 and over 11,300 to CVE-2026-110264, out of about 39,000 seen daily.
- Finder: joaxcar via HackerOne (GitLab release credits, CVE record); Ruby credits Johan Carlsson (joaxcar).
Sources
- GitLab patch release 19.4.2, 19.3.5, 19.2.8, 12/10/2026, checked 04/11/2026
- GitLab critical patch release 19.5.1 and backports, 21/10/2026, checked 04/11/2026
- GitLab patch release 19.5.3 and the rest, 29/10/2026, from GitLab's patch release feed, checked 04/11/2026
- GitLab: find the version you are running, checked 04/11/2026
- CVE.org, CVE-2026-97229
- CISA Known Exploited Vulnerabilities catalogue, version 2026.11.03, checked 04/11/2026
- Ruby: Regexp compilation fixes related to GitLab's CVEs, 23/10/2026, checked 04/11/2026
- Rapid7: CVE-2026-97229, 13/10/2026, updated 30/10/2026, checked 04/11/2026
- Alpine Linux: GitLab security incident, 28/10/2026, checked 04/11/2026
- BleepingComputer, 02/11/2026, tip-off, used only for the Shadowserver counts
- NCSC: disruptive cyber activity highlights risk from internet-exposed systems and edge devices, 27/08/2026, checked 04/11/2026
Read next
More from The Patch Wave
- Act today

iPhones, iPads and Macs: update today, Apple has patched a compression flaw already on the US exploited list
Apple's 09/11/2026 updates fix the Brotli flaw CVE-2026-111497, which CISA added to its exploited list on 27/10/2026, and an iMessage group chat flaw. Update iPhones, iPads and Macs today.
- Act today

Microsoft Outlook: November's updates fix a flaw attackers are already using
Microsoft says attackers are already using an Outlook flaw (CVE-2026-124194) fixed in this month's updates. Update Office and run Windows Update today.
- Watch

Hotmail and Outlook.com bounced some business email for nearly three days: Microsoft has fixed it
Microsoft says a faulty spam rule update made Outlook.com, Hotmail and Live wrongly block some email from 06/11 to 09/11/2026. It has rolled the update back. If your mail to those addresses still bounces, tell your IT person.