Multiple vulnerabilities in Regexp and String case conversion
- ID
- 48450
- Status
- summarized
- Published
- 19 Nov 2026, 7:52 AM
- Fetched
- 20 Nov 2026, 4:26 AM
- Provider
- Hacker News
- Category
- dev-community
- Original URL
- https://www.ruby-lang.org/en/news/2026/11/18/multiple-vulnerabilities-in-regexp-and-string/
- Source URL
- https://hnrss.org/best
Summary
- Score
- 7.5
- Created
- 20 Nov 2026, 4:27 AM
- Tags
- Audience
- developersvibe_coderssaas_founders
What happened
The Ruby core team published seven security advisories covering its regular expression engine and String case conversion, and says it is aware of proof-of-concept exploits showing some can achieve remote code execution. Fixes ship in Ruby 4.0.10, 3.4.13 and 3.3.14, with CVE IDs still pending so the advisory uses GHSA identifiers such as GHSA-34m4-m9fh-gqp5 (one-byte heap overflow in case conversion) and GHSA-7x2q-68qv-6p8x (double free in regex compilation). The thread drew 326 points and 126 comments on Hacker News.
Why it matters
If any service you run is on Ruby, the decision is binary: upgrade to 4.0.10, 3.4.13 or 3.3.14 now, not next sprint. The two conditions that make these exploitable are concrete — compiling attacker-controlled regex patterns (user-defined filters, validation rules, search syntax) and case-converting crafted strings (username/email normalisation, slug generation, i18n handling). Inventory which of your endpoints accept user regex or transform untrusted strings, and if you cannot patch immediately, disable or sandbox those paths first.
Discussion angle
Which of your features actually let users supply a regex pattern or push raw input through case conversion — and would you even know if one did? Worth walking through a real codebase live to see how often 'harmless' normalisation helpers touch untrusted strings.