"We are aware of PoCs that prove some of them can be used to trigger remote code execution," the maintainers said.
The seven flaws, and which carry remote-code-execution proofs
Ruby's maintainers disclosed seven memory-safety defects that affect its regular-expression engine and string case-conversion code. The project published a security announcement plus a separate advisory for each flaw, and rated them: three critical, three high and one moderate. For five of the seven, the project says proof-of-concept (PoC) exploits demonstrate that crafted input can run code on the machine.
- GHSA-34m4-m9fh-gqp5 — Critical. A one-byte heap overflow when Ruby changes the case of a string in certain single-byte encodings, such as ISO-8859-1 or Windows-1252. It has a remote-code-execution PoC. (GitHub advisory)
- GHSA-7x2q-68qv-6p8x — Critical. A double free when Ruby compiles a crafted regular expression that uses a character-class intersection (&&). It has a remote-code-execution PoC. (GitHub advisory)
- GHSA-3p8q-wmhx-vm2w — Critical. A heap overflow when the size of a compiled regular expression overflows during compilation. It has a remote-code-execution PoC. (GitHub advisory)
- GHSA-87fm-7w84-j2px — High. A heap overflow when a case change produces a result larger than 4 GiB. It has a remote-code-execution PoC, though the size needed puts it out of reach for most requests. (GitHub advisory)
- GHSA-7whj-cfh7-xgm4 — High. A heap overflow when Ruby turns a crafted compiled regular expression back into text with Regexp#to_s. It has a remote-code-execution PoC. (GitHub advisory)
- GHSA-wpqw-5qxg-m68r — High. An out-of-bounds read during case-insensitive matching. Its PoC shows attacker-controlled memory corruption; the maintainers say remote code execution is possible but has not been shown. (GitHub advisory)
- GHSA-pvgc-g7gj-pv6h — Moderate. An out-of-bounds read when Ruby matches a case-insensitive backreference against a crafted subject string. The advisory says it "may disclose memory contents or crash the process." (GitHub advisory)
Versions affected and the release patch strategy
The project released fixed interpreter versions yesterday: Ruby 4.0.10, 3.4.13 and 3.3.14. The affected ranges and fixes are:
- Ruby 4.0.0 through 4.0.9 — fixed in 4.0.10.
- Ruby 3.4.0 through 3.4.12 — fixed in 3.4.13.
- Ruby 3.3.13 and earlier — fixed in 3.3.14; with 3.3.14 the maintainers renamed the Ruby 3.3 phase from security maintenance to legacy maintenance, and support still ends at the end of March 2027.
- Ruby 3.2 and earlier — end of life and not fixed; the project recommends moving to a supported line.
The advisories do not yet have CVE numbers; the project says it has requested them, and until they are assigned the GitHub advisory IDs are the only way to track the flaws in scanners and inventories.

Your scanner finds 4,000 vulns. Which 12 matter?
Nubivance is a Rapid7 Registered Partner delivering vulnerability management as a service - scanning, risk-based prioritization, and remediation follow-through across IT and OT.
Fix the backlogHow applications become exposed
Because the flaws live inside Ruby itself, every application running a vulnerable interpreter is, in principle, exposed. Whether an attacker can reach a vulnerable code path depends on how the application handles external input, the maintainers said.
- The regular-expression bugs require an application that builds a regular expression from input an attacker controls and then compiles or runs it. Matching untrusted text against a fixed pattern written by developers does not pose the same risk, except for one noted case.
- The two case-conversion flaws fire when the application changes the case of a crafted string, so code that runs case conversion over imported or outside text is worth checking.
- The moderate read flaw fires when an application matches a crafted subject string against a fixed pattern that uses a case-insensitive backreference. The announcement and advisories do not include the PoC code.
Because the fixes are inside the Ruby interpreter, updating application gems or frameworks will not remove the vulnerability. The Ruby runtime on application servers, background workers and container images must be updated, and those hosts restarted or rebuilt to pick up the patched interpreter.
Who found the bugs, and the recent regular-expression patching context
The project credits Stephan Lipp of Ada Logics and Anthropic with four of the findings, and credits baba__yaga, aphantom, Hiroya Fujinami and Hiroshi SHIBATA with the other three. This is the second time in a month the project patched its regular-expression engine: on October 23 it shipped Ruby 4.0.9, 3.4.12 and 3.3.13 to patch compilation bugs that GitLab found.
Those October bugs were different from this week's seven. The October fixes sat behind four critical GitLab flaws; one of those drew an attempted attack on Alpine Linux's GitLab server and was later added to CISA's KEV catalog as actively exploited. The new advisories do not say that GitLab or any other named product can be attacked through this week's issues.
What this means for technologists, enterprise owners, and end users
- Technologists and security teams — Check whether your applications accept untrusted input that is compiled into regular expressions, and whether any code performs case conversion on imported or outside text. Plan to update interpreters to Ruby 4.0.10, 3.4.13 or 3.3.14 and rebuild or restart services to pick up the fixes.
- Enterprise operations and procurement leaders — Remember that updating gems or frameworks does not eliminate an interpreter-level vulnerability; inventories and container images must track the Ruby runtime version. Note that Ruby 3.2 and earlier will not receive fixes and the project recommends moving to a supported line.
- End users and the general public — The advisories report no attacks so far; exposure depends on whether an attacker can deliver crafted patterns or strings into an affected application.
The maintainers have published advisories and fixed interpreter releases; they have also requested CVE identifiers and supplied GitHub advisory IDs to track the flaws. For now, the factual record is straightforward: seven interpreter bugs, five with PoCs that demonstrate remote-code-execution potential, fixed interpreter releases available, and a firm reminder that interpreter updates — not just dependency upgrades — are what neutralize these specific risks.




