The GitLab vulnerability CVE-2026-97229 is being actively exploited; the U.S. agency CISA has listed it in its catalog of exploited vulnerabilities since October 29, 2026. This affects self-hosted GitLab installations used by machine builders, suppliers, intralogistics providers, and distributors to manage source code, control software, and build pipelines. IT management and software development leadership are now deciding whether the update is sufficient or whether they should audit the instance and, if in doubt, rebuild it.
Two vulnerabilities with a CVSS score of 10 out of 10 allow attackers to execute code on self-hosted GitLab servers. Install at least the versions released on October 21, such as 19.5.1, 19.4.3, or 19.3.6; if you have your own Ruby installation, also install Ruby 3.3.13, 3.4.12, or 4.0.9. The current versions are 19.5.6, 19.4.8, and 19.3.9, released on November 16. If the instance was accessible from the Internet and open to new accounts, this includes investigating the incident and changing the CI/CD credentials.
| Topic | What Applies |
|---|---|
| CVE-2026-97229 | CVSS 3.1: 10 out of 10 points according to GitLab, fixed in 19.2.8, 19.3.5, and 19.4.2 on October 12, 2026; actively exploited according to CISA; listed in the catalog since October 29, 2026 |
| CVE-2026-110264 | CVSS 3.1: 10 out of 10 points according to GitLab; affects all versions starting with 7.0; fixed in 18.11.13, 19.0.10, 19.1.9, 19.2.9, 19.3.6, 19.4.3, and 19.5.1 on October 21, 2026 |
| Latest Patch Versions | 19.5.6, 19.4.8, and 19.3.9, released on November 16, 2026, with 37 security fixes, plus GitLab Runner starting with version 19.5.1 |
| Your Own Ruby Installation | Fixed only in Ruby 3.3.13, 3.4.12, or 4.0.9, released on October 23, 2026 |
What Is Known About the GitLab Security Vulnerability
GitLab patched CVE-2026-97229 on October 12, 2026. The vulnerability lies in the regular expression compiler that GitLab uses when evaluating CI/CD configurations. An attacker could exploit this to execute code on the server; the vendor rates the vulnerability at 10 out of 10 points according to CVSS 3.1 (GitLab, October 12, 2026).
On October 21, CVE-2026-110264 was reported with the same severity rating. This second vulnerability affects all versions starting with 7.0; GitLab has backported the fix to version 18.11.13 (GitLab, October 21, 2026). Both bugs are in Onigmo, Ruby's regex engine. GitLab fixed the Ruby code in its own packages and images, and the Ruby developers followed suit on October 23 with Ruby 3.3.13, 3.4.12, and 4.0.9 (Ruby).
CISA added CVE-2026-97229 to its catalog on October 29 due to confirmed exploitation (CISA). Alpine Linux has disclosed a specific incident. On October 20 and 21, a newly registered account attacked the project’s instance, which was still running on version 19.3.4. The update to 19.3.6 did not close the vulnerability because the custom-built image used the standard Ruby. Alpine found no evidence of a successful attack but could not rule it out and rebuilt the instance by October 28 (Alpine Linux).
of the GitLab servers that Censys detected on the internet on October 13, 2026, were running a version vulnerable to CVE-2026-97229.
Censys, October 2026
That's 25,766 out of 82,454 detected hosts (Censys). Version numbers are counted.
What This Means for Development, Manufacturing, and the Supply Chain
A GitLab server runs the pipelines that build and ship firmware for controllers, software for test benches or extensions to warehouse management. Its CI/CD variables hold credentials for the registry, artifact storage and cloud accounts, often signing keys as well. For a successful attack, Alpine lists password hashes, 2FA secrets, CI/CD variables, runner tokens and private repositories, among other things, as potentially exposed.
A compromised build server can introduce vulnerabilities into the control software that is deployed. Since September 11, 2026, machine manufacturers have been required to report actively exploited vulnerabilities in their products in accordance with Article 14 of the Cyber Resilience Act.
Model Calculation: Effort for a Machine Builder’s GitLab Instance
The assumptions are arbitrary. A mechanical engineer is running a GitLab instance on version 19.3.4 using the vendor's packages, with 280 accounts, 12 of their own runners, and 160 CI/CD variables containing credentials. Registration is open to partner companies; the update to 19.3.6 was not released until October 24. We estimate that the update to 19.3.9, including testing on a copy, will take one to two person-days, and the investigation using GitLab’s detection rules and logs starting October 12 will take two to four person-days.
If logs are missing or show worker process crashes, rebuilding the server adds two to three person-days to the process. At 10 to 20 minutes per variable, replacing the 160 secrets takes 27 to 53 hours, or four to seven person-days. Re-registering the 12 runners is estimated to take two person-days. Without a rebuild, the estimate is 3 to 6 person-days; with a rebuild, it is 11 to 18 person-days.
Your Options: Effort, Costs, and Risks
| Option | Effort | Costs | Risk |
|---|---|---|---|
| Updating with packages from GitLab | Hours; one to two days, including testing | Minimal, maintenance window | Does not remove an attacker who has already breached the defenses |
| Updating Your Own Ruby Installation | Additionally, build Ruby 3.3.13, 3.4.12, or 4.0.9 | Low to moderate | Without a new version of Ruby, the vulnerability remains unpatched |
| Isolation Through a Registration Ban and VPN | Hours | Low | Does not protect against existing accounts |
| Check for traces | Two to four days, estimate | Internal or External Person-Days | According to Alpine, a successful attack remains invisible in the web logs |
| Rebuild and rotate secrets | 11 to 18 days, estimate | Highest internal costs | All users have to set up their access again |
| Switch to GitLab.com or GitLab Dedicated | Weeks | Licensing and Migration Costs | Data is held by the provider; leaked secrets remain valid |
| Do nothing | None | None for now | Access to source code and login credentials; possible breach of build and production networks |
GitLab Runner 19.5.1 has been included since October 29 because GitLab has revoked trust in compromised certificates from eMudhra (GitLab, October 29, 2026). How torck takes on such engagements is described on the page Professional Services for Software Operations.
Which Path Fits Which Instance
If the instance runs only on the internal network, without open registration, and was updated before October 21, updating to the latest patch version and running the detection rules is usually sufficient. If it was accessible from the Internet and open to external accounts, a forensic investigation is required. For custom-built images, check the Ruby version first.
If logs from October 12 onward are missing or show crashed worker processes, rebuild the instance, even if that takes two weeks. The vendor’s advisories are authoritative. Test updates in a test environment first.
GitLab situation report in three working daysFor each self-hosted instance, you receive the version, the Ruby version, internet exposure and account settings, an analysis of the detection rules and logs since October 12, and a list of all CI/CD variables, runner tokens and integrations that have to be rotated in a rebuild. You also receive a recommendation between update, forensic review and rebuild, with an effort estimate. You then decide whether your team updates, whether torck rebuilds the instance and which credentials are rotated immediately.
Frequently Asked Questions
Is updating to the latest version of GitLab enough?
For GitLab packages and images, it patches both vulnerabilities. If you’re using a custom Ruby installation, you’ll also need Ruby 3.3.13, 3.4.12, or 4.0.9. No update can remove an attacker who has already gained access.
How much does it cost to rebuild a GitLab instance that may have been compromised?
The effort involved depends primarily on the number of secrets. In our model calculation, which includes 160 CI/CD variables and 12 runners, the estimate ranges from 11 to 18 person-days, with four to seven of those person-days required solely for exchanging access credentials.
How can we tell if there's an attempted attack on GitLab?
GitLab has published six detection rules for CVE-2026-97229 and two for CVE-2026-110264, including crashed worker processes of the Regex engine. New accounts that immediately trigger CI configuration checks are considered suspicious.
The Next Step
torck analyzes, builds and operates software for industry and commerce, including platforms such as GitLab. Our approach is described on the page Professional Services: From Analysis to Operations. Related decisions are covered in the articles PHP2Shell: patch, isolate or replace PHP systems, Node2Shell and .NET 8 end of support and Reporting Requirements Under the Cyber Resilience Act. Schedule an Initial Consultation.
This article does not constitute legal advice. To determine whether and how these rules apply to your business, you should consult an attorney.