Issue #22502 has been updated by k0kubun (Takashi Kokubun). Status changed from Open to Closed At the dev-meeting on Nov 12th, @matz agreed that he will write the conclusion as a comment on this ticket. See also: [the meeting log](https://github.com/ruby/dev-meeting-log/blob/master/2026/DevMeeting-2026-11-...).
Request CVEs for the recent fixes
As per the policy decided by Matz, all these recent issues are now considered as vulnerabilities in Ruby itself. We have published GitHub Security Advisories for these issues, which we used for requesting CVEs: * https://github.com/ruby/ruby/security/advisories/GHSA-gfj3-8wj9-qx8p * https://github.com/ruby/ruby/security/advisories/GHSA-22mf-ggw7-pxfx * https://github.com/ruby/ruby/security/advisories/GHSA-qm4g-8pfh-6996 ---------------------------------------- Misc #22502: Clarify whether compiling an untrusted string into a Regexp is supported https://bugs.ruby-lang.org/issues/22502#change-120020 * Author: k0kubun (Takashi Kokubun) * Status: Closed ---------------------------------------- ## Proposal Decide whether compiling an untrusted string into a Regexp is a supported use case, and document the decision. * If it's not supported: * Document it in `Regexp.new` and [doc/security/security.rdoc](https://docs.ruby-lang.org/en/master/security/security_rdoc.html), like `Marshal.load` and `eval`. * Treat memory corruption bugs that only untrusted patterns can trigger as normal bugs. * If it's supported: * Treat such bugs as vulnerabilities. * Request CVEs for the recent fixes: [#13332](https://github.com/ruby/ruby/pull/13332), [#19020](https://github.com/ruby/ruby/pull/19020), and [#16801](https://github.com/ruby/ruby/pull/16801). ## Background * Ruby 4.0.9, 3.4.12, and 3.3.13 fixed Regexp compilation bugs that led to RCE on GitLab. GitLab assigned CVEs to them, but we haven't requested CVEs for Ruby itself. See [the announcement](https://www.ruby-lang.org/en/news/2026/10/23/regexp-fixes-for-gitlab-cves/). * The current documentation is not clear about it: * The [CVE-2022-28738 advisory](https://www.ruby-lang.org/en/news/2022/04/12/double-free-in-regexp-compilati...) says "in general, it is considered unsafe to create and use a Regexp object generated from untrusted input", but we still assigned a CVE to it. We did the same for CVE-2024-27282. * [The Regexp documentation](https://docs.ruby-lang.org/en/master/Regexp.html#class-Regexp-label-Timeouts) mentions untrusted sources only for DoS, and recommends `Regexp.timeout`. * It's not only `Regexp.new` and `/#{...}/`. `String#match` and `String#match?` also compile a String argument, e.g. `"str".match?(user_input)`. -- https://bugs.ruby-lang.org/