Ruby 4.0.10 Fixes Seven Memory Bugs, 26 Days After the Regex Patch Behind Four GitLab CVEs
Software / news
Ruby 4.0.10 Fixes Seven Memory Bugs, 26 Days After the Regex Patch Behind Four GitLab CVEs
Four of the seven advisories credit Stephan Lipp of Ada Logics and Anthropic, and Ruby still has no CVE numbers for any of them.
Ruby shipped 4.0.10, 3.4.13 and 3.3.14 on Nov. 18, 2026, fixing seven memory-safety bugs in its regular-expression engine and string case conversion. Several of the seven may allow remote code execution, according to the Ruby advisory.
The advisory, posted by mame under the title "Security advisories: multiple vulnerabilities in Regexp and String case conversion", recommends upgrading promptly. It follows the Oct. 23 releases of 4.0.9, 3.4.12 and 3.3.13, 26 days earlier.
Which Ruby versions are affected
Ruby 3.3.13 and earlier, 3.4.0 through 3.4.12, and 4.0.0 through 4.0.9 are vulnerable. Fixed releases are 4.0.10, 3.4.13 and 3.3.14. Ruby 3.3 is in security maintenance. Ruby 3.2 and earlier are end of life and receive nothing, and The Hacker News gave April 1, 2026 as the 3.2 end-of-life date when the October round shipped.
The advisory page gives no CVSS scores and no workarounds. It says CVE IDs have been requested but not assigned, and it identifies each bug by a GitHub advisory number instead. I could not open the linked GitHub advisory pages, so the severity ratings are not confirmed here.
The seven bugs, by advisory
| Advisory | Flaw | Credited to |
|---|---|---|
| GHSA-34m4-m9fh-gqp5 | One-byte heap overflow in string case conversion | Stephan Lipp (Ada Logics), Anthropic |
| GHSA-7x2q-68qv-6p8x | Double free compiling a crafted regex | Stephan Lipp (Ada Logics), Anthropic |
| GHSA-87fm-7w84-j2px | Integer overflow in case conversion, heap overflow | baba__yaga (HackerOne) |
| GHSA-wpqw-5qxg-m68r | Out-of-bounds read in case-insensitive matching | Stephan Lipp (Ada Logics), Anthropic |
| GHSA-3p8q-wmhx-vm2w | Integer overflow in regex compilation, heap overflow | aphantom (HackerOne) |
| GHSA-7whj-cfh7-xgm4 | Heap overflow in Regexp#to_s | Stephan Lipp (Ada Logics), Anthropic |
| GHSA-pvgc-g7gj-pv6h | Out-of-bounds read in case-insensitive backreference matching | Hiroya Fujinami, Hiroshi SHIBATA |
The advisory says proofs of concept exist showing code execution is possible for several of these. It does not say which ones beyond the per-bug descriptions, which mention possible code execution for the string case-conversion overflows, the regex double free, the compilation overflow and Regexp#to_s.
- Stephan Lipp (Ada Logics) and Anthropic4 advisories
- HackerOne researchers2 advisories
- Hiroya Fujinami and Hiroshi SHIBATA1 advisories
Source: Ruby security advisory of Nov. 18, 2026, ruby-lang.org, accessed 2026-11-19
What the Oct. 23 round fixed
The first round was triggered by GitLab. The Hacker News reported on Oct. 23 that three bugs in Onigmo, Ruby's regex engine, sat behind four GitLab CVEs. Two, disclosed Sept. 23, were rated 9.9 and needed a logged-in account. CVE-2026-97229 and CVE-2026-110264 were rated 10.0 and needed none. The reporter was a researcher using the handle joaxcar, through GitLab's bug bounty.
Ruby's own October advisory said an application is exposed if it compiles a regex from an attacker-controlled string, through Regexp.new, Regexp.union, Regexp.compile or interpolation such as /#{input}/. Setting Regexp.timeout did not stop those bugs. Whether the November regex bugs share that exposure condition is not addressed on the new advisory page, so apply the same caution until it is.
The October round also left a gap that the November one repeats. Ruby did not request its own CVE IDs, and GitLab's records name only GitLab as the affected product, so a scanner that matches installed Ruby versions against CVE data may not flag either round.
The advisory's own date problem
The advisory is dated Nov. 18 in the Ruby news listing, while its history section reads "Originally published at 2026-11-19 00:00:00 (UTC)." Both dates are on the page. Treat Nov. 18 as the day the releases and post appeared.
Another project that patched on a published date without CVE numbers was PHP, covered in PHP's critical security release for Nov. 19. A network-facing example from the same week is nginx2root and CVE-2026-123007.
If you run Ruby 3.4 or 4.0 in production: upgrade to 3.4.13 or 4.0.10 this week, and check how your scanner handles advisories without CVE IDs. If you are still on 3.2 or earlier, no fix is coming from Ruby, and a version upgrade is the only route.
Sources
More in Software
- 01OpenAI's WebRTC Voice Stack Draws a 30 ms Objection That Its Own Engineers Never AddressedLuke Curley says WebRTC drops audio older than 30 ms. OpenAI's engineers wrote about port ranges and routing, which is a different problem.
- 02Superpowers Passes 322,000 GitHub Stars as a Set of 15 Prompted Skills for 16 Coding AgentsJesse Vincent's MIT-licensed framework tells agents to brainstorm, plan and test first. Its clone count is large, and its evidence for better results is one author's view.
- 03GitHub Disables 144 Picofly Repositories After a Nintendo Notice Names OneThe November 6 notice is the first on GitHub aimed at Switch modchip firmware, and it asked for forks to be taken down without listing a single one.
- 04Chrome's Gemini Nano Download: What Google's Docs Say, and the Numbers They Leave OutGoogle's page on built-in model management gives triggers, a 30-day rule and full-download updates, but no file size, no disk threshold and no consumer off switch.