· via Hacker News – Front Page (hnrss.org)
Seven Ruby vulnerabilities with RCE proofs patched across three release lines
Ruby has fixed seven flaws in its regex engine and string case conversion, several with working remote code execution proofs, releasing 4.0.10, 3.4.13 and 3.3.14 and urging all users to upgrade.

What happened
The Ruby project has patched seven security vulnerabilities in its regular expression engine and its string case conversion routines, and it says proof-of-concept exploits exist showing that several of them can achieve remote code execution. The advisory, published on ruby-lang.org on 18 November 2026, announces three simultaneous fix releases — Ruby 4.0.10, 3.4.13 and 3.3.14 — and strongly recommends that everyone upgrade.
CVE identifiers have been requested but not yet assigned, so the advisory tracks the issues by their GitHub Security Advisory (GHSA) identifiers instead.
The regular expression flaws
Five of the seven bugs sit in Ruby's regex engine:
- GHSA-7x2q-68qv-6p8x: a double free during pattern compilation. Applications that compile regular expressions supplied by an attacker are at risk, and RCE proofs exist.
- GHSA-3p8q-wmhx-vm2w: an integer overflow during pattern compilation that results in a heap buffer overflow, again targeting applications that compile attacker-controlled patterns. RCE proofs exist.
- GHSA-wpqw-5qxg-m68r: an out-of-bounds read during case-insensitive matching. According to the advisory, this can corrupt memory in a manner the attacker controls, and RCE proofs exist.
- GHSA-7whj-cfh7-xgm4: a heap buffer overflow in Regexp#to_s. Converting a crafted pattern to a string may disclose information or allow remote code execution in applications that compile attacker-controlled patterns.
- GHSA-pvgc-g7gj-pv6h: an out-of-bounds read in case-insensitive backreference matching. This one is limited to disclosing memory contents or crashing the process.
The case conversion flaws
The remaining two bugs involve String case conversion:
- GHSA-34m4-m9fh-gqp5: a single-byte heap buffer overflow triggered by changing the case of a crafted string. RCE proofs exist.
- GHSA-87fm-7w84-j2px: an integer overflow in case conversion that also produces a heap buffer overflow, with RCE proofs.
Because these two are reached through ordinary string operations rather than through compiling patterns, the exposure is especially broad: any code path that changes the case of untrusted input is a potential trigger.
Affected versions and fixes
According to ruby-lang.org, the vulnerable ranges are Ruby 3.3.13 and earlier, Ruby 3.4.0 through 3.4.12, and Ruby 4.0.0 through 4.0.9. The fixed releases are 4.0.10, 3.4.13 and 3.3.14.
Ruby 3.3 is in its security maintenance phase. Ruby 3.2 and older have reached end of life and will not receive these fixes, so anyone running those versions has no option but to move to a supported branch to be protected.
Who reported the bugs
The advisory credits four of the seven issues to Stephan Lipp of Ada Logics together with Anthropic. The remaining three were reported by baba__yaga, by aphantom, and by Hiroya Fujinami with Hiroshi Shibata. The notice was posted by mame.
Why it matters
Regular expressions and case conversion are ubiquitous, low-visibility operations. Ruby applications routinely run pattern matching and case conversion on user-supplied input — routing, validation, normalization — so the pool of potentially affected code is very large. Several of these bugs come with demonstrated remote code execution rather than theoretical risk, which puts them in patch-immediately territory rather than schedule-a-maintenance-window territory.
Two secondary points stand out. First, with CVE numbers still pending, vulnerability scanners and dependency policies that key off CVE identifiers may not yet flag the exposure; the reliable signal right now is the Ruby version number. Second, the cluster of findings credited jointly to a human researcher at Ada Logics and Anthropic is a notable data point for machine-assisted auditing of memory-safety bugs in long-standing C code — and a regex engine paired with Unicode string handling is exactly the kind of pointer-heavy codebase where that approach appears to be paying off.
- #ruby
- #security
- #vulnerabilities
- #regex
- #open-source