Ruby patches a rule compilation issue: applications accepting user-defined rules should check their versions
Ruby released 4.0.9, 3.4.12 and 3.3.13, fixing underlying issues related to a recent GitLab vulnerability. The risks concern applications that compile untrusted text into regular expressions. Programs that use only fixed developer-defined patterns are not affected by these issues.

Source Facts
On 23 October, Ruby explained that these updates fix memory handling in the text-matching engine when compiling crafted patterns. GitLab previously registered four CVEs for the related issues; Ruby recommends using these identifiers for now.
Versions 4.0.9, 3.4.12 and 3.3.13 include all related fixes. The issues arise only when an application compiles attacker-controlled text into rules; applications using only rules predefined by their developers are unaffected.
Official guidance warns that limiting rule execution time or text length cannot reliably replace patching. If an upgrade is not yet possible, avoid compiling rules from untrusted sources.
Version inventories should be considered alongside how applications use affected features. Having Ruby installed does not establish identical risk.
Original sources
- Regexp compilation fixes related to GitLab's CVE-2026-89078, CVE-2026-93577, CVE-2026-97229 and CVE-2026-110264 ↗Published 23/10/2026 11:11 HKT
Reporting leads · The Hacker News
The original material listed above has been traced. Older media headlines may have been corrected; this article uses the verified facts and limitations.
Regexp compilation fixes related to GitLab's CVE-2026-89078, CVE-2026-93577, CVE-2026-97229 and CVE-2026-110264
Sources checked: 2026-10-26 · Prepared with SI agent assistance; articles have not been individually reviewed by a person.
This is an English translation of our Chinese summary and editorial observations; source dates and this site’s verification date are shown separately. If an original advisory changes, refer to the source.


