Ruby fixes seven regex and string flaws, five with code-execution proofs
The Ruby project released Ruby 4.0.10, 3.4.13 and 3.3.14 on November 18, fixing seven memory-safety flaws in its regex engine and string case conversion. Five have proof-of-concept code execution; no attacks are reported.
Warden, covering security, outages and the rules for tech
, 3 min read
5 of 7Ruby flaws with a code-execution proof of concept
What to know
- Ruby 4.0.10, 3.4.13 and 3.3.14 shipped November 18; Ruby 3.2 and older are end of life and get no fix.
- Three flaws are rated critical, three high and one moderate; none had a CVE ID yet, only GitHub advisory IDs.
- The regex flaws matter where an app compiles a pattern built from untrusted input; no exploitation has been reported.
The line that decides whether this is an emergency for a given Rails shop is short: does the app ever build a regular expression out of text a user typed? If it does, three of the seven bugs Ruby fixed on November 18 can turn that pattern into code running on the server. If it only matches user text against patterns a developer wrote, most of this release is a routine upgrade.
Ruby 4.0.10, 3.4.13 and 3.3.14 fix all seven, according to The Hacker News, which summarized the project's announcement and its seven GitHub security advisories. We could not load ruby-lang.org or the advisories themselves, so the details below are the Hacker News account.
What is broken
Six of the flaws sit in Ruby's regex engine and its string case conversion; the seventh is in case-insensitive matching. Three are rated critical: a double free when compiling a regex that uses a character-class intersection (&&), a heap overflow when a compiled pattern's size overflows during compilation, and a one-byte heap overflow when changing the case of a string in a single-byte encoding such as ISO-8859-1 or Windows-1252.
Three more are high: a heap overflow in Regexp#to_s when it turns a crafted compiled pattern back into text, a heap overflow when a case change produces a result over 4 GiB, and an out-of-bounds read during case-insensitive matching. The last is moderate, an out-of-bounds read that the advisory says "may disclose memory contents or crash the process."
Five of the seven come with a working proof of concept for remote code execution: the three criticals, the Regexp#to_s bug and the 4 GiB case-change bug, though that last one needs an input too large to be practical in most web requests. None has a CVE ID yet; the project has asked for them, so the GitHub advisory IDs (GHSA-34m4-m9fh-gqp5, GHSA-7x2q-68qv-6p8x, GHSA-3p8q-wmhx-vm2w and four others) are what scanners will key on for now.
Who has to act
Anyone on Ruby 4.0.0 to 4.0.9, 3.4.0 to 3.4.12 or 3.3.13 and earlier. Ruby 3.3 now moves to legacy maintenance, with support ending at the end of March 2027. Ruby 3.2 and anything older is end of life and gets no fix at all, which makes this release one more reason to finish that migration.
The case-conversion bugs widen the exposure beyond regex. They trigger when an app upcases or downcases crafted text, the sort of thing import jobs and normalization code do to external data without anyone thinking of it as risky.
No attacks have been reported. Four of the seven findings are credited to Ada Logics and Anthropic.
The second round in four weeks
This is not the first patch to Ruby's regex engine this autumn. Ruby 4.0.9, 3.4.12 and 3.3.13 shipped on October 23 with fixes for three other regex compile bugs found by GitLab; the Hacker News says the seven fixed now are different. That is two security releases for the same component 26 days apart. Teams that pinned to the October versions and called the job done are already one release behind.
It lands the same week as PHP's 18-CVE security release and the Java4Shell OpenJDK flaw: three language runtimes, three rounds of host-level patching that application code can't do for itself. Without CVE IDs there are no CVSS scores yet either; our guide to CVSS and how to read a security advisory explain what to look for when they arrive. The question to watch is whether a public exploit for the regex criticals turns up before the distribution packages do.
Sources
- Ruby Releases Fixes for 7 Regex and String Flaws, Warns 5 Have Proof-of-Concept RCE, The Hacker News, November 19, 2026
Internet, outages and securityAnthropic
Written by an AI correspondent under standards set by editor Jacob Knight. Spotted an error? Tell us and we will fix it.