Ruby has released versions 4.0.10, 3.4.13 and 3.3.14 to fix seven flaws in its regular expression engine and in the case conversion of strings, the core project said in an advisory posted on 18 November 2026. “We are aware of PoCs that prove some of them can be used to trigger remote code execution,” the advisory says. “We strongly recommend upgrading.”
Version 3.2 and earlier have reached end of life and “will not receive these fixes.” There has been no report of exploitation in the wild, and the flaws are not listed in CISA’s Known Exploited Vulnerabilities catalogue, version 2026.11.18.
In brief
- Seven flaws in regexp handling and string case conversion are fixed in Ruby 4.0.10, 3.4.13 and 3.3.14. Ruby 3.3.13 and earlier, 3.4.0 to 3.4.12, and 4.0.0 to 4.0.9 are listed as affected.
- The most closely watched of the seven is a one-byte heap overflow in string case conversion, tracked as GHSA-34m4-m9fh-gqp5. Official advisories say proof-of-concept work shows remote code execution in some scenarios.
- Veria Labs says the same bug is reachable without authentication in default Rails and classic-style Sinatra, and lists several self-hosted products as bundling an affected interpreter. Those claims are Veria’s, not vendor confirmations. The firm says it will publish a proof of concept in a week.
The one-byte overflow hits single-byte encodings, not UTF-8
The project has asked for CVE identifiers but says they have not been assigned yet, so the official notes use GitHub Security Advisory identifiers. GHSA-34m4-m9fh-gqp5, published as Critical on 19 November, describes “a one-byte heap-based buffer overflow in the case conversion of strings.” “When changing the case of a string in some single-byte encodings, such as ISO-8859-1 and Windows-1252, the interpreter could write one byte past the end of the output buffer.” “Changing the case of a crafted string may allow remote code execution.” The advisory credits Stephan Lipp of Ada Logics, and Anthropic.
Veria Labs, which brands the same bug ruby2ßhell, says UTF-8 strings “take a different code path and are not affected.” It also says the overflow is reached by common case-conversion methods on an affected interpreter. The firm’s page, updated at 13:29 GMT on 19 November, argues that the bug “is reachable from the following frameworks in their default configuration,” naming Rails and classic-style Sinatra, and that other frameworks and plain Rack are “not exposed by default.” A table on the same page lists GitLab 19.6.0 (Ruby 3.3.13), GitHub Enterprise Server 3.22.5 (Ruby 4.0.9) and Chatwoot 4.20.0 (Ruby 3.4.4) as bundling an affected interpreter, while Mastodon 4.7.6, OpenProject 17.9.8 and a Discourse base image are listed as already on 4.0.10. Those rows are Veria’s checks, not statements from the product vendors. Veria says it will “be publishing a proof of concept in a week, once people have had time to upgrade.”
The other six official advisories cover a double free and heap overflows in regular-expression compilation, an integer overflow in case conversion, out-of-bounds reads in case-insensitive matching, and a heap overflow in Regexp#to_s. Several of those, the project says, may allow remote code execution in applications that compile or match attacker-controlled patterns. All seven are fixed in the same three releases. The 3.3 branch remains in its security-maintenance phase, which is why 3.3.14 was issued; everything older than that line is out of support.
A researcher’s Rails claim is not the same as Ruby’s wording
The upgrade advice is straightforward for anyone who can move: install 4.0.10, 3.4.13 or 3.3.14. The harder cases are the ones the project has already named. Applications still on 3.2 or earlier will not get these patches, so the practical choices are to migrate or to take the application off the network. Self-hosted products that ship their own interpreter need a vendor build, not only a language-level note, and Veria’s table should be read as a prompt to check those vendors, not as a substitute for their advisories.
The most tempting sentence in circulation is the idea of unauthenticated remote code execution on a stock Rails application. Veria puts that claim in public. Ruby’s own wording is narrower: it knows of proofs of concept that trigger remote code execution “in some scenarios.” Those two statements can both be true, and they are not the same statement. Until a vendor, or the core project, describes a default Rails request path in its own advisory, the cautious reading is the official one, plus a reminder that Veria says it will release a public proof of concept in a week. That is a reason to patch now, not a reason to treat the researcher page as a completed incident report.
TSN has already followed how regex bugs in the web stack move from advisory to, sometimes, real attacks. GitLab’s CVSS 10.0 CI regex flaw was serious enough on paper; Alpine Linux later had to rebuild its GitLab after an attack on that CVE. Rails’ own recent Active Storage fixes are a reminder that framework releases and language releases can travel on different clocks. The useful next facts here are a vendor confirmation from GitLab, GitHub Enterprise or Chatwoot, an assigned CVE, a CISA KEV listing, or evidence of exploitation. Until one of those arrives, the action is the one the project has already given: upgrade, if a fixed branch is still available.
Sources
- Ruby, “Security advisories: multiple vulnerabilities in Regexp and String case conversion,” posted by mame, 18 November 2026
- GitHub Security Advisory GHSA-34m4-m9fh-gqp5, “Heap buffer overflow in case conversion of strings,” 19 November 2026
- Veria Labs, “Ruby2Shell (GHSA-34m4-m9fh-gqp5),” updated 19 November 2026, 13:29 UTC
- CISA, Known Exploited Vulnerabilities catalogue, version 2026.11.18, 18 November 2026, 19:17 GMT
Get TSN’s biggest tech stories, explained.
News and insights across AI, tech, crypto and cybersecurity. Every source linked. Unsubscribe anytime.
Get the newsletterRelated stories
Rails Security Releases Fix Critical Active Storage Flaw is the closest TSN neighbour on a recent Rails security release, and the right next stop for readers asking how framework patches sit beside a language-level fix.
- GitLab Patches CVE-2026-97229, a CVSS 10.0 Flaw That Could Let an Unauthenticated User Run Code Through a Crafted CI/CD Regex is the nearer comparison for a regex bug in a widely deployed Ruby stack.
- Alpine Linux Rebuilds Its GitLab After Attack on CVE-2026-97229 shows what can follow when a regex execution flaw is not only patched but later used.
Follow @tsnmediahub on X for breaking AI news as it happens.
Follow on X


