Run ruby -v. Ruby’s project has published seven memory-safety flaws: some in its regular expression engine, some in the case conversion of strings. The fixes are in 4.0.10, 3.4.13 and 3.3.14.
It is “aware of PoCs that prove some of them can be used to trigger remote code execution”, and recommends upgrading.
Why this reaches ordinary web code
Ruby runs under a lot of what people self-host: GitLab, Mastodon, Discourse and Redmine.
The two easiest triggers are routine request handling. Case conversion is one, since downcase and upcase on user input is ordinary work in search normalisation, tag handling or comparing email addresses. Compiling attacker-controlled patterns is the other, through Regexp.new or case-insensitive matching against hostile input.
No setting turns these off. The mitigation is a runtime upgrade.
The seven
The advisory tabulates all seven. Two carry the shortest path to code execution. One is a heap buffer overflow in case conversion (GHSA-34m4-m9fh-gqp5). The other is a double free in regexp compilation (GHSA-7x2q-68qv-6p8x), which hits applications “that compile attacker-controlled patterns”.
Two more are integer overflows that end in heap overflows. The last three are out-of-bounds reads in case-insensitive matching and backreference matching, and a heap overflow in Regexp#to_s.
Which versions, and which get nothing
Affected: 3.3.13 and earlier, 3.4.0 through 3.4.12, and 4.0.0 through 4.0.9. Fixed: 4.0.10, 3.4.13 and 3.3.14.
“Ruby 3.3 is in the security maintenance phase.” And: “Ruby 3.2 and earlier have reached their end of life and will not receive these fixes.”
If an application pins an end-of-life Ruby, its own vendor has to move.
Containers need a rebuild
Mastodon, GitLab and similar projects ship images that bundle their own Ruby. A host upgrade does nothing for the Ruby inside a container.
Whether those projects have published rebuilt images was not checked here, so this claims nothing either way. Watch the image, not the host.
The scanner gap
No CVE identifiers exist. The advisory says so: “CVE identifiers have been requested for these vulnerabilities but have not been assigned yet, so this advisory refers to them by their GitHub Security Advisory (GHSA) identifiers.”
Scanners keyed on CVE feeds will not report this, and a quiet dashboard is not evidence of a patched runtime. Search the GHSAs instead.
Distributions lag, and that is not a verdict
Debian’s tracker lists ruby3.3 across five suites. Testing and unstable carry 3.3.8-2.2. Stable carries 3.3.8-2, while stable-security and stable-proposed-updates carry 3.3.13-0+deb13u1, so the security archive is ahead of the stable branch.
The tracker also flags a newer upstream version, 3.3.13.
Read that against the ranges: 3.3.13 and earlier are affected, and 3.3.14 is the release that fixes them. A 3.3.13 build has not reached the fix by version number alone, and whether the vendor backported the patches is a question for its own advisory. Fedora and Alpine were not investigated.
What this is not
The advisory carries no CVSS score, so no severity number appears here.
Proof-of-concept code is the vendor’s own statement. No in-the-wild exploitation is reported in any source read here.
The advisory is stamped 2026-11-19 00:00:00 UTC, the evening of 18 November on the American east coast. That stamp is the date cited here.
Sources: Ruby’s security advisory, the release notes for 4.0.10, 3.4.13 and 3.3.14, and Debian’s ruby3.3 tracker, all read on 18 November 2026.

