A perfect 10.0 severity score is great in gymnastics. In security, it is the score nobody wants. GitLab fixed that kind of flaw on Wednesday, and the company’s own patch notice says anyone running the software on their own servers should upgrade immediately. That is the short version of this GitLab critical patch release. The longer version explains why developers are buzzing about it, and why it matters even if you have never typed a line of code.
Let’s start with what we actually know. And what we don’t.

What the GitLab critical patch release fixes
GitLab is the tool many companies use to store their source code and run the automated pipelines that ship it. On October 21, the company pushed out new versions: 19.5.1, 19.4.3, 19.3.6, 19.2.9, 19.1.9, 19.0.10 and 18.11.13. Together, they fix 12 vulnerabilities.
One of them is the headline. GitLab tracks it as CVE-2026-110264, and it scores a perfect 10.0 on the standard severity scale. According to GitLab, it is an integer overflow in the software’s regular expression compiler. Under certain conditions, a specially crafted expression could let someone with no login run their own code on the GitLab server.
Read that again. No password. No account. Just access to the server over a network.
However, GitLab has not said what those conditions are. That’s a gap, and it matters.
Who the GitLab critical vulnerability actually hits
Here’s the part the panicky headlines skip. This GitLab critical vulnerability only hits self-managed GitLab, meaning companies that run the software on their own servers. GitLab.com, the hosted service, is already patched. GitLab Dedicated customers on the fixed internal versions need to do nothing, according to the company.
So if you use GitLab.com, you can relax. If your employer runs its own copy, someone on the IT team has homework today.
The affected range is huge, though. Every version from 7.0 up to the patched releases is vulnerable, per GitLab’s notice. That reaches back to 2014. A very old server is a very exposed server.
The buried detail: this GitLab security patch is round two
About nine days earlier, GitLab fixed another maximum-severity bug in a related part of the same regex machinery, BleepingComputer reported. That one is CVE-2026-97229, patched around October 12. The same researcher, who goes by joaxcar, reported both through GitLab’s bug bounty program.
Servers that installed the October 12 update are still vulnerable to this new flaw, according to security advisories tracking the release. So “I already patched last week” does not cut it. This latest GitLab security patch is a separate job.
It also isn’t a clean sweep. The Hacker News, a security news site, notes that four of the fixed versions are older than the ones GitLab normally patches. That suggests the company took the unusual step of protecting people who had fallen behind.
Is anyone exploiting the GitLab CVSS 10.0 flaw?
No sign of that so far. GitLab has not reported attacks, and the flaw was not on the U.S. government’s list of known exploited vulnerabilities as of Wednesday night, according to The Hacker News. A public exploit database also listed no available exploit when we checked.
A “could allow” bug is not the same as a “was used” bug. Still, a GitLab CVSS 10.0 flaw with no login required is the kind of hole attackers read patch notes to find. That is why the clock matters. Recent headlines, such as hackers turning supermarket fridges into ovens, show how quickly attackers can turn one weak spot into real-world damage.
What this GitLab emergency update means for you
If your company self-hosts GitLab, that server holds its source code, its secrets and the keys to how it builds and ships software. A compromised build server is a nasty place to start a day, for the company and for the customers who rely on what it ships. Treat this GitLab emergency update like the real emergency it is.
The fix is not painless. The patch includes database migrations, so single-node setups will see downtime during the upgrade, per GitLab. Larger setups can use zero-downtime procedures. Plan for it, but don’t use it as an excuse to wait.
If you are not sure whether your employer is affected, ask. One short question to your IT team beats a long incident report later. For more on why security stories keep reshaping the business world, see how Proofpoint’s $6.3 billion bet on Varonis is playing out.
What happens next
GitLab says the issue details go public on its tracker 90 days after the patch, which works out to around January 19, 2027. The next scheduled patch releases land on the second and fourth Wednesdays, so look for November 11 and November 25. Meanwhile, watch for a government exploitation warning, a public proof of concept, or any update from GitLab on attacks.
And if you run an old GitLab server nobody has touched in years, that’s the one to check first. A flaw that reaches back to 2014 doesn’t care how old your box is.






