GitLab Server Flaw Exploited: 1,000+ Still Unpatched

Source, with the title GitLab Server Flaw Under Attack
Photo: Elchinator on Pixabay

Attackers are exploiting a maximum-severity GitLab server flaw, and more than 1,000 internet-exposed servers are still unpatched, BleepingComputer reported on Nov. 2. The flaw lets an attacker run their own commands on the server without logging in.

GitLab is a tool software teams use to store and manage their code. Most small offices around Orting, Puyallup and Sumner don’t run it. But if you hire a developer, a web shop or an IT vendor, they might. This one is worth a quick question.

What happened

GitLab released fixes on Oct. 12. Three weeks later, the security group Shadowserver says it still sees more than 1,000 servers open to the flaw.

On Friday, the US Cybersecurity and Infrastructure Security Agency (CISA) confirmed that attackers are using it in the wild. CISA added it to its Known Exploited Vulnerabilities list. Its deadline for federal agencies was Sunday. That deadline only binds federal agencies. But CISA’s list is a good “patch these first” guide for everyone else.

The facts

The flaw is tracked as CVE-2026-97229. It’s an “integer overflow,” which is a math error in software. It sits in the part of GitLab that reads regular expressions (short text patterns) in pipeline settings. Pipelines are the automatic steps that build and test code.

GitLab says a specially crafted pattern could let an unauthenticated person run code on the server. “Unauthenticated” means no password needed. This kind of bug is called remote code execution.

ProductAffectedFixed
GitLab Community Edition and Enterprise Edition (self-managed)Versions older than the patched releases19.4.2, 19.3.5, 19.2.8

The exploitation report comes from CISA’s catalog, as relayed by BleepingComputer. The count of unpatched servers comes from Shadowserver.

There’s more. BleepingComputer says a different maximum-severity GitLab bug, CVE-2026-110264, is still open on over 11,300 servers, according to Shadowserver. So “patch GitLab” is not a one-time job.

Why this GitLab server flaw matters to small offices

Most readers can relax. GitLab says GitLab.com is already running the patched version. GitLab Dedicated users don’t need to act.

You should check if any of these is true:

  • Someone set up GitLab on a server for you, in your office, at a host or in the cloud.
  • Your web developer or IT vendor keeps your code or website projects on their own GitLab.
  • You run it yourself for a side project and forgot about it.

A code server holds more than code. If attackers get in, they may reach passwords, keys and secrets stored for automated jobs. From there they can reach your website, your cloud accounts or your customer records. That is why a forgotten server is a real risk.

A lesson from Alpine Linux

BleepingComputer also covered the Alpine Linux project. Attackers tried this flaw against its GitLab server on Oct. 20–21. Alpine says it found no evidence that code ran or that its software was tampered with. But it couldn’t rule it out because of missing logs. So it rebuilt the server from scratch and reset all passwords.

The patching story is the useful part. Alpine first installed 19.3.4 instead of the fixed 19.3.5. A later upgrade to 19.3.6 still didn’t close the hole. The fix also needed a patch to Ruby, which GitLab’s official packages bundle but Alpine’s custom container image did not.

The takeaway: “we updated” isn’t the same as “we’re fixed.” If your GitLab runs in a custom setup, ask how it was built.

Patching fast takes steady habits. We wrote about how we go from alert to patch and about what same-day patching takes.

What to do this week

  • Ask the question. Email your web developer or IT vendor: “Do we use a self-managed GitLab server? If so, is it on 19.4.2, 19.3.5, 19.2.8 or newer?”
  • Check the version yourself if you run it. Sign in as an admin and look at the version on the Help page. If it’s older than the fixed releases, update now.
  • Confirm the fix really took. Don’t stop at the version number. If you use custom containers or packages, check that the vendor’s full fix is in the build.
  • Look at who can reach it. If GitLab doesn’t need to be open to the whole internet, limit access to your office or a VPN (a private, encrypted tunnel).
  • Rotate secrets if you were exposed. If the server was unpatched and online since Oct. 12, change passwords and any keys or tokens stored in it. Turn on two-factor sign-in where you can.
  • Keep a list. Write down every server and tool your business runs, and who updates each one.

Not sure what you have?

If you can’t answer “do we run GitLab?” with confidence, that’s normal, and it’s worth sorting out. We offer a free 30-minute assessment. We look at your computers, email and backups and tell you what to fix first. There’s no cost and no contract. You can also see how we help with security and patching.

Sources

This article was drafted by Percival, Rainier IT’s AI writing assistant, from the sources linked above, and reviewed by Christopher Engelhardt before publication. Spot an error? Email [email protected].

$ share

Percival AI

Rainier IT

Rainier IT

$ leave_a_comment

Your email is never shown. Comments are read before they appear.

Protected by reCAPTCHA. Google's Privacy Policy and Terms apply.