TLDR

  • Ruby released versions 4.0.10, 3.4.13 and 3.3.14 to fix seven security flaws.

  • Several of the bugs can allow remote code execution in some scenarios.

  • Updating Rails or other gems will not install the fixed Ruby runtime.

  • No CVE numbers were assigned at publication, so the flaws use GitHub advisory IDs.

  • Ruby 3.2 and older branches are past end of life and will not get the fixes.


Developers running Ruby applications need to update the language runtime itself after maintainers released fixes for seven security flaws on November 19, 2026. Updating Rails or other gem dependencies will not install the patched code.

The new releases are Ruby 4.0.10, 3.4.13 and 3.3.14. They fix bugs in the regular expression engine and in the code that changes the case of text.

According to the Ruby security advisory, several of the flaws can allow remote code execution. That means an attacker could run code inside a vulnerable Ruby process.

The maintainers said they know of proof-of-concept demonstrations that achieved code execution in some scenarios. These were research demonstrations, not confirmed attacks on production systems.

Flaws Tracked Without CVE Numbers

At the time of publication, the Ruby team had requested CVE numbers, but none had been assigned. The bugs are being tracked by their GitHub Security Advisory IDs instead.

Two flaws affect the code that changes text case. One, GHSA-34m4-m9fh-gqp5, lets Ruby write one byte past the memory set aside for its output in some text encodings.

The other, GHSA-87fm-7w84-j2px, begins with an integer overflow, where a calculation goes beyond the range it can store. This leads to a write outside the intended memory area, and both case-conversion bugs can allow code execution in some scenarios.

Five flaws affect regular expressions, which apps use to search or check text. A double-free bug, GHSA-7x2q-68qv-6p8x, makes Ruby release the same block of memory twice while compiling a pattern.

A buffer overflow tracked as GHSA-3p8q-wmhx-vm2w also occurs during compilation. Both compilation bugs can lead to code execution when an app compiles patterns supplied by an attacker.

Another buffer overflow, GHSA-7whj-cfh7-xgm4, happens when Regexp#to_s turns a regular expression into text. It can expose information or allow code execution.

GHSA-wpqw-5qxg-m68r involves reading past the intended memory area during case-insensitive matching. A demonstration showed attacker-controlled memory corruption, though code execution was not shown for this flaw.

The last flaw, GHSA-pvgc-g7gj-pv6h, can expose memory contents or crash the process. It occurs during case-insensitive matching that reuses text captured earlier in the pattern.

Which Versions Are Affected

Affected versions are Ruby 3.3.13 and earlier, 3.4.0 through 3.4.12, and 4.0.0 through 4.0.9. Users on those branches should move to 3.3.14, 3.4.13 or 4.0.10. Ruby 3.3 is in security maintenance.

Ruby 3.2 and older branches have reached end of life. They will not receive these fixes, so teams still using them need to move to a supported branch.

Because the patches apply to the runtime, they are separate from earlier Rails flaws involving Active Storage file reads and image uploads. Teams are advised to check the Ruby version in each environment where an app runs, not just on developer laptops.

Internet-facing services that accept user-defined patterns or change the case of incoming text should be updated first. An app does not need to use every affected feature to be exposed.

After upgrading, teams should rebuild container images that still bundle an older runtime. Web services and background workers then need to be redeployed and checked to confirm they run a patched version.