Ruby: trace untrusted text to the interpreter that runs it
Ruby’s fixes cover regular expressions and text case conversion. Businesses need to identify the inputs reaching those operations and prove that the responsible services were updated.
Читать на португальскомIn this article
By Pentesty
What the maintainers confirmed
The Cyber Security Brazil report, published November 19, points to the official Ruby fixes. The project recommends 4.0.10, 3.4.13 or 3.3.14 for seven flaws in Regexp and String conversion. Five have remote code execution PoCs in some scenarios; another has PoCs demonstrating attacker-controlled memory corruption. The remaining flaw can disclose memory or crash the process. The reviewed sources do not confirm observed exploitation, which does not prove its absence.
When checked on November 19, CVE assignments were still pending. Use the GHSA identifiers to track the advisories. The aggregate advisory displays Posted on November 18 and records original publication on November 19 at 00:00 UTC in its History. Keep these fields separate from this analysis’s editorial date.
Separate the expression pattern from its subject text
For Pentesty’s proposed triage, record who controls the pattern, who supplies the text and which encoding reaches Ruby. Some flaws require expressions built from attacker-controlled patterns. That condition deserves attention in configurable filters, search features and integrations accepting customer-supplied expressions. Do not assume every use of Regexp provides the same attack path.
Case conversion also belongs in this inventory. One flaw involves certain single-byte encodings; another requires a converted result exceeding 4 GiB. The backreference advisory describes a crafted subject string without requiring the attacker to supply the pattern. Using a fixed expression does not close this part of the review.
Map each application to its fixed branch
The project lists Ruby 3.3.13 and earlier, 3.4.0 through 3.4.12, and 4.0.0 through 4.0.9 as affected. Map web servers, queues, importers, scheduled jobs and build images to the corrected version for their branch. Updating gems or a framework does not, by itself, demonstrate that the interpreter was replaced.
The 3.3.14 release and current branches index call Ruby 3.3’s phase legacy maintenance, including selected bug fixes. The aggregate advisory still uses security maintenance. Support remains scheduled to end March 31, 2027. The project will not provide these fixes for Ruby 3.2 or earlier.
Set acceptance criteria for the process still serving users
For each deployment, request evidence of the installed package or build, the image used and replacement of old processes. Check replicas, persistent workers and environments receiving traffic through different routes. Where a vendor provides backports, connect the build to its correction bulletin; comparing its number with the upstream version alone may be insufficient.
The reasoning resembles our analysis of patching the running PHP service: the change needs to reach the process serving the application. Our discussion of OpenSSL libraries loaded by services extends this check to dependencies actually in use. Retain an owner, timestamp, evidence and outstanding work for each group of instances.
Validate behavior without reproducing the attack
Run authorized regression tests using ordinary inputs, accepted encodings, searches, validation and imports used by the business. Check errors, queue processing and worker recovery. Running PoCs or generating enormous inputs is unnecessary to demonstrate deployment. Record which paths were not exercised as well.
After the change, monitor unexpected termination and processing failures. Update evidence confirms deployment coverage, not the absence of an earlier compromise. If suspicious signs exist, preserve records and initiate an investigation within a defined scope. Keep retirement of unsupported versions as a separate decision with an owner and a deadline.
Frequently asked questions
Is every Ruby application exposed to RCE?
The advisories describe different conditions. Assess third-party-controlled patterns, incoming text and conversions performed. The cited PoCs establish RCE in some scenarios, without demonstrating universal exploitability.
Does a fixed regular expression remove the risk?
The backreference advisory involves crafted text and does not require an attacker-supplied pattern. Separate String conversion flaws also exist. Keep these paths within the assessment.
How can a backported package be checked?
Connect the installed build to the vendor’s bulletin and confirm that processes use that build. Evidence needs to identify the service and the deployment’s coverage.
Did Ruby 3.3 receive a new support deadline?
Release 3.3.14 renamed the phase legacy maintenance and expanded the accepted types of fixes. The end of support remains scheduled for March 2027.
Sources and references
- Cyber Security Brazil: editorial news reference
- Ruby: seven Regexp and String conversion flaws, Posted November 18 and History November 19, 2026 UTC
- Ruby GHSA-34m4-m9fh-gqp5: case conversion in single-byte encodings
- Ruby GHSA-87fm-7w84-j2px: overflow when converting large strings
- Ruby GHSA-wpqw-5qxg-m68r: case-insensitive matching
- Ruby GHSA-pvgc-g7gj-pv6h: out-of-bounds reads in backreferences
- Ruby: release 4.0.10, Posted November 18, 2026
- Ruby: release 3.4.13, Posted November 18, 2026
- Ruby: release 3.3.14 and legacy maintenance, Posted November 18, 2026
- Ruby: branch maintenance, consulted November 19, 2026
Original Pentesty analysis, published November 19, 2026. The proposed scenarios are editorial guidance, with scope and validation to be defined for each environment.