IPCRIME | November 19, 2026. The Ruby language project has issued an unusually broad security advisory covering seven defects in its string case-conversion and regular-expression internals. Some have proof-of-concept demonstrations showing that crafted inputs can lead to remote code execution under the appropriate application conditions. The fixes are available in Ruby 4.0.10, 3.4.13 and 3.3.14.
The project’s November 18 announcement, originally published at midnight UTC on November 19, advises users to upgrade promptly. CVE numbers had been requested but were not assigned when the advisory was written, so the flaws are identified through GitHub Security Advisory (GHSA) references. A public proof of concept demonstrates feasibility in a scenario; it does not automatically establish active exploitation of production systems.
What the seven issues affect
The disclosures include heap-buffer overflows and an integer overflow in case conversion, a double-free and heap-buffer overflows in regular-expression compilation, and out-of-bounds reads in case-insensitive matching or backreference processing. A specially crafted pattern or string reaches the vulnerable operation only when an application actually passes such material into the relevant runtime code path.
- GHSA-34m4-m9fh-gqp5: one-byte heap-buffer overflow during string case conversion.
- GHSA-7x2q-68qv-6p8x: double-free in regular-expression compilation.
- GHSA-87fm-7w84-j2px: integer-overflow-triggered heap-buffer overflow during case conversion.
- GHSA-wpqw-5qxg-m68r: out-of-bounds read in case-insensitive regular-expression matching.
- GHSA-3p8q-wmhx-vm2w: integer overflow leading to heap-buffer overflow when compiling regular expressions.
- GHSA-7whj-cfh7-xgm4: heap-buffer overflow in
Regexp#to_s. - GHSA-pvgc-g7gj-pv6h: out-of-bounds read in case-insensitive backreference matching.
Affected and fixed branches
Ruby lists the affected releases as 3.3.13 and earlier in the 3.3 line, 3.4.0 through 3.4.12, and 4.0.0 through 4.0.9. The maintenance releases 3.3.14, 3.4.13 and 4.0.10 respectively contain the fixes. Ruby 3.2 and older versions are out of maintenance and do not receive these updates.
Development teams should not assume that installing a newer Ruby command-line executable upgrades the interpreter used by every service. Inspect runtime versions inside containers, application deployment artifacts, CI/CD images and managed environments, then rebuild, restart and confirm the versions that actually execute production requests.
What operators should prioritize
First identify services where untrusted users can influence regular-expression patterns or case-conversion inputs; those paths deserve early testing. Then upgrade supported Ruby runtimes, pin safe base images and rerun application tests. If an upgrade is temporarily blocked, reduce untrusted input exposure and apply process isolation and privilege restrictions, but do not claim those controls eliminate the vulnerability.
At the time of this report, the official advisory establishes affected branches, fixes and proof-of-concept potential; it does not claim confirmed in-the-wild exploitation. IPCRIME will distinguish any future exploitation reporting from the existence of public test code.
Primary sources
Ruby project — security advisory covering all seven issues; Ruby — official downloads and supported versions; Ruby 4.0.10 official release note.