Ruby Fixed Seven Memory Bugs in Regexp and String Case Conversion. Its Maintainers Say PoCs Prove RCE for Five. Upgrade to 4.0.10, 3.4.13 or 3.3.14
If you run Ruby, upgrade today: 4.0.10, 3.4.13 or 3.3.14, whichever matches your branch. Ruby 3.2 and earlier will not get these fixes. If you are on 3.2 or older, the fix is a branch upgrade, not a patch.
The Ruby team published the advisory around midnight UTC between November 18 and 19, 2026, with the three releases alongside it. It covers seven flaws: five in the regular expression engine and two in string case conversion (the code behind upcase, downcase, capitalize and swapcase). The advisory's own words: "We are aware of PoCs that prove some of them can be used to trigger remote code execution."
That is the maintainers' wording, not the press's. The Hacker News headline ("Warns 5 Have Proof-of-Concept RCE") matches the per-flaw text: five of the seven advisories say PoCs prove RCE "in some scenarios," a sixth says its PoC shows "memory corruption in an attacker-controlled way," and the seventh is a memory read or crash. Neither the advisory nor the seven GitHub advisories we read says anyone is exploiting these in the wild. PoCs exist. Exploitation has not been reported. As far as we could tell, the PoCs themselves have not been published.
What is affected and what fixes it
The Ruby team's table, the same for all seven flaws:
Ruby 3.3.13 and earlier: fixed in 3.3.14.
Ruby 3.4.0 through 3.4.12: fixed in 3.4.13.
Ruby 4.0.0 through 4.0.9: fixed in 4.0.10.
Ruby 3.2 and earlier: end of life, no fix.
There are no CVE numbers yet. The advisory says: "CVE identifiers have been requested for these vulnerabilities but have not been assigned yet." It refers to them by GitHub Security Advisory (GHSA) IDs. That matters for scanners, more on that below.
The seven flaws, and what input reaches each one
The question that decides your exposure: does an attacker need to control the regular expression pattern, or only a string? Here is what each advisory says.
Attacker-controlled pattern needed (four flaws). These hit apps that build a Regexp from user input.
GHSA-7x2q-68qv-6p8x, rated critical by the Ruby team: double free when compiling a pattern with a character class intersection (the "&&" syntax inside brackets). "Compiling a crafted regular expression pattern may allow remote code execution in applications that compile attacker-controlled patterns." PoC proves RCE in some scenarios.
GHSA-3p8q-wmhx-vm2w, critical: integer overflow in the size of the compiled pattern, leading to a heap buffer overflow. Same condition: attacker-controlled patterns. PoC proves RCE in some scenarios.
GHSA-7whj-cfh7-xgm4, high: heap buffer overflow in Regexp#to_s, the call that turns a compiled pattern back into text. "May allow information disclosure or remote code execution in applications that compile attacker-controlled patterns." PoC proves RCE in some scenarios.
GHSA-wpqw-5qxg-m68r, high: out-of-bounds read in case-insensitive matching, which "can lead to memory corruption." Affects "applications that use regular expressions built from attacker-controlled strings." The PoC proves memory corruption "in an attacker-controlled way." This one does not claim RCE was demonstrated.
Only an attacker-controlled string needed (three flaws). These are broader, because ordinary apps change the case of user input constantly.
GHSA-34m4-m9fh-gqp5, critical: a one-byte heap overflow when changing the case of a string "in some single-byte encodings, such as ISO-8859-1 and Windows-1252." PoC proves RCE in some scenarios. Our reading, not the advisory's: most web apps handle text as UTF-8, so the exposed code is the code that transcodes or force-encodes input into Latin-1 or Windows-1252 and then changes its case. Legacy imports, CSV handling, email and old database bridges are where to look.
GHSA-87fm-7w84-j2px, high: integer overflow when the case-converted result "exceeds 4 GiB." PoC proves RCE in some scenarios. Our reading: a web request body that large is rare behind normal size limits, but batch jobs and file processors that upcase or downcase whole files are a different story.
GHSA-pvgc-g7gj-pv6h, medium: out-of-bounds read in case-insensitive backreference matching. "Matching a crafted string may disclose memory contents or crash the process." No RCE claim. This one needs only the subject string, against a pattern that uses a case-insensitive backreference.
Credits, per the advisory: four of the seven went to Stephan Lipp (Ada Logics) and Anthropic, two to HackerOne researchers baba__yaga and aphantom, and one to Hiroya Fujinami and Hiroshi SHIBATA.
Who is exposed
Apps that turn user input into a Regexp. Search boxes with a "regex" option, user-defined filter or routing rules, log and alert rule editors, admin tools that take a pattern, anything calling Regexp.new or Regexp.union on request data. Code review platforms and CI systems are the classic case. Ruby's previous release round, on October 23, was titled "Regexp compilation fixes related to GitLab's CVE-2026-89078, CVE-2026-93577, CVE-2026-97229 and CVE-2026-110264." This class of input has already produced CVEs downstream once this fall.
Rails apps. Rails is not named in the advisory, and the bugs are in Ruby, not Rails. But every Rails app runs on one of the affected interpreters and changes the case of user strings all day. Whether a given app reaches the narrow conditions above (single-byte encodings, very large strings, user-built patterns) is an app-by-app question. Patch the interpreter rather than trying to prove you are unreachable.
Containers. Your image carries its own Ruby. Patching the host does nothing for it. The official Docker Hub ruby image already lists 4.0.10, 3.4.13 and 3.3.14 tags (we checked the 4.0.10-slim, 3.4.13-slim and 3.3.14-slim tags today). Images pinned to an older exact version, or built from a base you have not pulled since Wednesday, are still on vulnerable code.
Distribution packages. If your Ruby comes from apt, dnf, apk or Homebrew, the version string will not tell you much: distributions backport fixes into older version numbers. Check the package changelog. The catch this week is that there are no CVE IDs yet, and distribution security trackers key on CVE IDs. Until they are assigned, look for the GHSA IDs or the words "Regexp" and "case conversion" in the changelog, and watch your distribution's security list. We did not check any distribution's packages for this post.
Am I affected?
Run ruby -v in each environment that serves traffic, including inside the container: docker exec into the running container, not the host. Anything below 4.0.10, 3.4.13 or 3.3.14 on its branch is affected. 3.2 and older are affected with no fix.
Open .ruby-version and the "ruby" line in your Gemfile (and Gemfile.lock's RUBY VERSION section). Bump them, or your next deploy can quietly pin you back.
Check the FROM line in every Dockerfile. A tag like ruby:3.4 moves when you pull it; a tag like ruby:3.4.12-slim never will. Rebuild and redeploy; a new tag does nothing for a running container.
Search your code for Regexp.new, Regexp.union and string interpolation inside regex literals that takes request, params, header or file content. Those are the call sites the four pattern-side flaws need. Regexp.escape limits what user text can express, but the advisories do not say it blocks these bugs, so do not treat it as a substitute for upgrading.
Search for force_encoding and encode calls targeting ISO-8859-1, Windows-1252 or other single-byte encodings, followed by upcase, downcase, capitalize or swapcase. That is the path the critical case-conversion flaw describes.
For distribution packages, read the changelog for the GHSA IDs above (or CVE IDs once they are assigned), not the version number.
What our edge can and cannot see
Nothing here is visible at the network edge. These are bugs inside the Ruby process, triggered by what an app does with input it has already accepted. An exploit would arrive as an ordinary form field, upload or API body. There is no URL path, scanner signature or user agent to match, and no PoC has been published to fingerprint. Our edge shield and honeypots cannot tell you whether you were targeted. The fix is the upgrade.
No indicators were published in the sources we read, so we added nothing to the feed for this one.
How we know
We read the Ruby team's advisory and its three release announcements on ruby-lang.org, and the seven GitHub Security Advisories on the ruby/ruby repository, which carry the affected ranges, patched versions, severity ratings and weakness classes quoted above. The GitHub release for 4.0.10 is timestamped 23:35 UTC on November 18. The advisory's history line says it was published at 00:00 UTC on November 19. The Hacker News article is the press report; we used it only to compare wording. What we did not verify: whether any PoC is public, whether any distribution has shipped fixed packages, and when CVE IDs will be assigned.
Sources
Ruby: Security advisories: multiple vulnerabilities in Regexp and String case conversion, https://www.ruby-lang.org/en/news/2026/11/18/multiple-vulnerabilities-in-regexp-and-string/
Ruby 4.0.10 Released, https://www.ruby-lang.org/en/news/2026/11/18/ruby-4-0-10-released/
Ruby 3.4.13 Released, https://www.ruby-lang.org/en/news/2026/11/18/ruby-3-4-13-released/
Ruby 3.3.14 Released, https://www.ruby-lang.org/en/news/2026/11/18/ruby-3-3-14-released/
GitHub Security Advisories, ruby/ruby: https://github.com/ruby/ruby/security/advisories
The Hacker News: Ruby Releases Fixes for 7 Regex and String Flaws, Warns 5 Have Proof-of-Concept RCE, https://thehackernews.com/2026/11/ruby-releases-fixes-for-7-regex-and.html
Read next: the last time a Ruby-world fix and a public exploit raced each other, in Rails Held the Exploit Details Until August 28. A Working PoC Was on GitHub the Same Day.
Every indicator in this post is in the feed. Free.
1.58M+ IOCs, STIX 2.1 / TAXII, 88% novel vs ThreatFox, exploited-CVE leads ahead of CISA. No credit card — a free API key in 30 seconds, and you can audit every claim above against the live endpoints.



Comments