A Regex Compiler Became A Way In
GitLab fixed CVE-2026-97229 on 12 October, a CVSS 10.0 integer overflow in the compiler that handles regular expressions in CI/CD pipeline configuration. Under certain conditions, GitLab's advisory says, an unauthenticated user could run arbitrary code on the GitLab server through a specially crafted regular expression in a CI/CD configuration.
The advisory doesn't spell out those conditions, and none of the three reports we read does either. A researcher using the handle joaxcar reported the flaw through GitLab's HackerOne bug bounty programme. GitLab.com already runs the patched version and GitLab Dedicated customers need take no action, but administrators of self-managed instances must update at once. As of 13 October, heise reports, GitLab had communicated no attacks.
| Release line | Vulnerable | Fixed in |
|---|---|---|
| GitLab 19.2 | Before 19.2.8 | 19.2.8 |
| GitLab 19.3 | Before 19.3.5 | 19.3.5 |
| GitLab 19.4 | Before 19.4.2 | 19.4.2 |
Three high-severity bugs were fixed in the same release. CVE-2026-92883 (8.7) is a cross-site scripting flaw. CVE-2026-16301 (8.5) lets a user with the Developer role run pipelines on protected branches. CVE-2026-14814 (8.2) can poison cached responses and potentially expose protected environment variables. Heise counts five high-severity flaws in all.
Three Critical GitLab Flaws In A Few Weeks
CVE-2026-97229 is GitLab's third critical flaw in recent weeks, and the September one showed how fast attackers move.
| CVE | CVSS | Component | Reported consequence |
|---|---|---|---|
| CVE-2026-85706 | 10.0 | GitLab CE and EE | Unauthenticated reading of sensitive data such as credentials and secrets, with probes within hours of disclosure and a CISA listing a day after the fix |
| CVE-2026-90970 | 9.9 | AI Gateway | An authenticated user with Duo Agent Platform access could break out of the prompt template sandbox and run commands |
| CVE-2026-97229 | 10.0 | CI/CD regular expression compiler | Unauthenticated code execution, with no attacks reported as of 13 October |
After the September flaw, CISA gave US federal agencies three days to secure their systems. It has flagged five GitLab flaws abused in attacks since November 2021, one of them used by ransomware gangs. No attacks on the new flaw had been reported by 13 October, but September's record is the pace to plan for.
Why A Pipeline Server Is Worth Attacking
A CI/CD server sits between source code and production, which is why code execution on it is worth more to an attacker than on most business servers.
It typically holds the secrets pipelines need to build, test and deploy, such as access tokens and deploy keys, and it can change what ships to customers. GitLab says it has more than 30 million registered users and that more than 50 percent of the Fortune 100 use it. Self-hosting trades convenience for control over where your code and data sit, and it moves the patching duty to you. That can be a deliberate choice for teams with data-residency requirements, and it's also why a vendor's patch day becomes your deadline.
A 72-Hour Plan For Self-Managed Teams
Treat this as a 72-hour job for every internet-reachable instance, and start with the version check.
First, read your installed version and compare it with 19.2.8, 19.3.5 and 19.4.2, then confirm the exact build numbers in GitLab's own advisory. Second, schedule the upgrade within 72 hours, starting with any instance reachable from the internet. Third, until it's done, limit who can reach the server and who can edit CI/CD configuration files.
Fourth, if you can't rule out exposure, rotate the secrets stored as pipeline variables once the patch is in. Fifth, subscribe to GitLab's security advisories so the next one reaches a person on the day. The 72 hours is our suggested window and not a GitLab deadline.
Read next: Two Config Lines Show If NetScaler's New Bug Hits You | GitLab's Worst-Rated Flaw Needs Just One Public Project
