← All security news
SecurityPatchCRITICAL

Update Ruby now: 4.0.10, 3.4.13 and 3.3.14 fix seven regex and string bugs, and Ruby says proof-of-concept exploits reach code execution

· 1 min read

Ruby fixed seven memory-safety flaws in its regular expression engine and string case conversion on 18 November 2026. The Ruby team says it knows of PoCs that turn some of them into remote code execution. Ruby 3.2 and older get no fix.

Ruby

On 18 November 2026 the Ruby core team released Ruby 4.0.10, 3.4.13 and 3.3.14 to fix seven vulnerabilities in Ruby's regular expression engine and in string case conversion. The advisory says: "We are aware of PoCs that prove some of them can be used to trigger remote code execution", and the team "strongly recommend[s] upgrading".

Affected: Ruby 3.3.13 and earlier, 3.4.0 to 3.4.12, and 4.0.0 to 4.0.9. Ruby 3.3 is in security maintenance; Ruby 3.2 and older are end-of-life and will not get these fixes. No CVE IDs have been assigned yet: CVEs were requested, and the flaws are tracked by GitHub advisory IDs such as GHSA-34m4-m9fh-gqp5 and GHSA-7x2q-68qv-6p8x.

What the bugs are: heap buffer overflows, a double free, integer overflows and out-of-bounds reads. Most of them matter to applications that compile regular expressions from attacker-controlled text (search filters, validation rules). Two are different: they sit in string case conversion, so a crafted string alone may be enough, with no crafted pattern. One more can leak memory or crash the process through case-insensitive backreference matching. SecurityOnline rates three of the seven critical and reports PoCs for six of them, five reaching code execution; Ruby has not published the PoCs.

No exploitation in the wild has been reported. Four of the seven flaws are credited to Stephan Lipp of Ada Logics together with Anthropic; others came through HackerOne and from Ruby developers. This follows Ruby's October regex fixes (4.0.9, 3.4.12, 3.3.13), which were tied to remote code execution flaws in GitLab.

More news