November 19, 2026
A Plain Text File Could Let Attackers Run Code on Your Ruby Site. Have You Upgraded?
If your website runs on Ruby, including many Rails apps, a security fix landed on 18 November 2026 that site owners should not treat as a…

By HackerMe
3 min read
If your website runs on Ruby, including many Rails apps, a security fix landed on 18 November 2026 that site owners should not treat as a routine patch. The Ruby team says it fixed seven memory-safety flaws in the regular-expression engine and in how Ruby changes the case of text, and that it knows of proof-of-concept code showing that some of these flaws can be used to run code remotely. Ruby Central adds an important detail for ordinary businesses: some of the bugs can be triggered by everyday text handling, such as a legacy-encoded email or an imported file, not only by an obviously hostile upload.
What happened
On 18 November 2026 the Ruby project published a security advisory and released Ruby 4.0.10, 3.4.13 and 3.3.14. The same notice was shared on the oss-security mailing list.
The advisory says: "Seven vulnerabilities have been discovered in Ruby's regular expression engine and in the case conversion of strings. We are aware of PoCs that prove some of them can be used to trigger remote code execution." It strongly recommends upgrading.
Identifiers have been requested but had not been assigned when the advisory was published, so the Ruby team refers to each issue by a GitHub Security Advisory identifier. This article does not describe how the flaws work in practice.
Who is affected
The official advisory says these versions are affected:
- Ruby 4.0.0 through 4.0.9
- Ruby 3.4.0 through 3.4.12
- Ruby 3.3.13 and earlier
The fixed versions are 4.0.10, 3.4.13 and 3.3.14.
Ruby 3.3 is in the security maintenance phase. The advisory says Ruby 3.2 and earlier have reached end of life and will not receive these fixes. If a site is still on those older versions, the only path the Ruby team and Ruby Central describe is to move to a supported release that includes the fix.
Ruby Central says the official advisory is the source of truth and that it does not list a workaround: "Upgrading is the fix."
Why a plain text file is part of this story
Four of the seven flaws involve regular expressions, which often matter most when an application builds patterns from untrusted input. Ruby Central says two others are different. They are memory-safety bugs in the case conversion of strings, and the advisory says that changing the case of a crafted string may allow remote code execution.
Ruby Central adds that one of those case-conversion bugs applies to strings in some single-byte encodings, such as ISO-8859–1 and Windows-1252, and the other applies when the converted result exceeds 4 GiB. "If your application handles legacy-encoded text, such as email or imported files, an ordinary case conversion could be the trigger."
That is the site-owner version of the problem: the risky input may look like a normal document or message, not like an attack tool. This article does not describe how to craft such a file.
The seventh issue, the advisory says, can disclose memory contents or crash the process.
None of the sources we read mention attacks using these flaws in the wild. That is not a reason to wait. Once a patch is public, the people who write attack tools can compare the old and new code.
What site owners should do
This is not only a problem for teams that write Ruby themselves. It also applies to Rails apps, to hosts that install Ruby for you, and to container images that bundle a Ruby version.
We explain the usual split in what your host handles and what you still need to check. Today's critical PHP security update is the same kind of question: who actually installs the new version on your server? If your Ruby comes from a container image, an outdated image can keep an old Ruby on a site that looks up to date in the control panel, a risk we also covered in a quieter way in Docker Hub leaked keys.
1. Ask which Ruby version is running
Not the version in a document from last year. The version that is running on the live site.
2. Ask when it will be upgraded
On a supported 4.0, 3.4 or 3.3 branch, that means 4.0.10, 3.4.13 or 3.3.14. On Ruby 3.2 or older, it means moving to a supported version that includes the fix.
3. Ask who will rebuild and redeploy
If Ruby comes from a Linux package, a container image or a hosting platform, Ruby Central says to watch for an updated package or image, then rebuild and redeploy. A host that "will patch it" is not the same as a host that has already shipped a new image and restarted your app.
4. See what strangers see
An update fixes the language your site runs on. It does not tell you what else the site exposes. A free website security scanner can show what an outsider can see from the internet, without logging in.
FAQ
Does this affect WordPress sites?
WordPress runs on PHP, not Ruby. This update matters if you also have a Ruby or Rails app, a tool built in Ruby, or a host or container that ships Ruby.
Is there a temporary setting I can turn off until we upgrade?
The official advisory does not list a workaround. Ruby Central says upgrading is the fix.
Were these flaws already used in attacks?
None of the sources we read mention attacks in the wild. The Ruby team does say it knows of proof-of-concept code showing remote code execution in some scenarios, which is why the upgrade is urgent.
Originally published at https://security.hackerme.ai on November 19, 2026.