The Ruby maintainers released versions 4.0.10, 3.4.13 and 3.3.14 on November 18, fixing seven memory-safety bugs in the interpreter’s regular expression engine and string case conversion. Maintainers say they know of proof-of-concept code showing that some of the flaws can trigger remote code execution, five of seven according to one report.
Seven Bugs Rated Critical, High and Moderate
The advisories rate three of the flaws critical, three high and one moderate. None has a CVE identifier yet, so the advisories use GitHub advisory IDs. They include GHSA-7whj-cfh7-xgm4, a heap overflow in Regexp#to_s, and GHSA-87fm-7w84-j2px, a case-conversion flaw triggered by results larger than 4 GiB. GHSA-wpqw-5qxg-m68r is an out-of-bounds read with attacker-controlled corruption, and GHSA-pvgc-g7gj-pv6h is a medium-severity read through a case-insensitive backreference.
The affected lines are Ruby 4.0, 3.4 and 3.3. Older lines receive no fix.
Ada Logics, Anthropic and Others Credited for the Ruby Bugs
Four of the findings are credited to Stephan Lipp of Ada Logics and Anthropic. The remaining reports came from baba__yaga, aphantom, Hiroya Fujinami and Hiroshi SHIBATA.
Memory-safety bugs of this kind, heap overflows and out-of-bounds reads, are the class of flaw that lets corrupted memory be steered toward code execution, which is why the maintainers took the proof-of-concept reports seriously enough to ship releases across three active lines at once.
Exposure Depends on Whether an App Handles External Input
The regular-expression flaws require an application that compiles attacker-controlled patterns. The two case-conversion bugs are different: they can fire from a crafted string alone, so any application that changes the case of external input is a potential target without needing to compile attacker-supplied patterns.
That difference widens the realistic exposure for case-conversion flaws. Applications that pass user-provided text through upcasing or downcasing are common, so exposure is not limited to unusual designs.
Second Regex Fix Batch in Four Weeks
The release is the second regular-expression fix batch in four weeks. Ruby versions 4.0.9, 3.4.12 and 3.3.13, released on October 23, fixed bugs behind four critical GitLab flaws. One of those was attempted against Alpine Linux’s GitLab server and was added to CISA’s Known Exploited Vulnerabilities catalog.
The maintainers state that the newly fixed bugs are different from the October ones. No attacks have been reported against the November flaws, and no workaround exists.
Why the October GitLab Precedent Draws Attention
The October episode showed that a flaw in the language runtime can propagate into large applications built on it, in that case GitLab, and that attackers will test such flaws against real targets. Whether the November set follows the same path depends on whether researchers or attackers connect the interpreter bugs to widely deployed Ruby applications.
Ruby Interpreter Upgrades Rather Than Gem Updates
Because the bugs live in the interpreter itself, updating individual gems does not address them. The fix requires upgrading the Ruby interpreter, restarting processes and rebuilding container images that embed an affected version. Maintainers also point to Regexp.escape for handling user input as a defensive measure in application code.
Ruby 3.3 Enters Legacy Maintenance
Ruby 3.3 now moves to legacy maintenance, with support ending at the close of March 2027. Organizations still on that line have roughly four months of support remaining. Teams on lines older than 3.3 get no fix and have no patched version to move to without changing branches.
Every application running on an affected Ruby version carries the bugs, and the practical risk for each depends on how it treats external input. The combination of five reported proof-of-concept exploits and a short interval since the previous batch makes this an update that production teams are likely to prioritize.
