Ruby maintainers shipped emergency patches across three active language branches after security researchers demonstrated working code-execution exploits against core string and regular expression routines.
According to the official Ruby security advisory published Wednesday, versions 4.0.10, 3.4.13, and 3.3.14 close seven memory-safety defects. Maintainers rated three issues critical, three high, and one moderate.
While no active exploitation has been confirmed, proof-of-concept (PoC) exploits exist for five bugs. "We are aware of PoCs that prove some of them can be used to trigger remote code execution," Ruby maintainers warned in the advisory.
| Advisory ID | Severity | Affected Component | Vulnerability Type | Maximum Impact |
| GHSA-34m4-m9fh-gqp5 | Critical | String case conversion | One-byte heap overflow | Remote code execution (RCE) |
| GHSA-7x2q-68qv-6p8x | Critical | Regex compilation | Double free | Remote code execution (RCE) |
| GHSA-3p8q-wmhx-vm2w | Critical | Regex compilation | Integer/heap overflow | Remote code execution (RCE) |
| GHSA-87fm-7w84-j2px | High | String case conversion | Integer/heap overflow | Remote code execution (RCE) |
| GHSA-7whj-cfh7-xgm4 | High | Regexp#to_s | Heap buffer overflow | Info disclosure or RCE |
| GHSA-wpqw-5qxg-m68r | High | Case-insensitive regex | Out-of-bounds read | Memory corruption |
| GHSA-pvgc-g7gj-pv6h | Moderate | Backreference regex | Out-of-bounds read | Info disclosure or crash |
The most urgent defect, tracked as GHSA-34m4-m9fh-gqp5 (CVE-2026-132825) and dubbed "ruby2ßhell," triggers a heap overflow when changing string case in legacy single-byte encodings like ISO-8859-1 or Windows-1252.
Per Veria Labs, UTF-8 strings do not trigger this bug, though default Ruby on Rails and classic-style Sinatra apps face unauthenticated network exposure when handling those legacy encodings.
Why runtime bugs create operational blind spots
Standard Ruby security workflows revolve around updating application gems, yet these defects live inside the C-level language interpreter itself. Simply running bundle update will not remediate an exposed server.
Furthermore, this marks the second major Ruby regex security release in under a month, following Oct. 23 patches for flaws that underpinned critical GitLab bugs, one of which later faced attempted exploitation against Alpine Linux.
When core parsing primitives repeatedly fail under crafted input, organizations relying on bundled runtimes face prolonged exposure windows while waiting for downstream software vendors to repackage containers.
How this affects Ruby users and operations teams
Enterprise infrastructure teams, SaaS providers, and developers running self-hosted Ruby applications must audit the actual runtime binary executing in production, not just manifest files.
- Affected releases: Ruby 4.0.0 through 4.0.9, 3.4.0 through 3.4.12, and 3.3.13 and earlier require immediate upgrades to 4.0.10, 3.4.13, or 3.3.14.
- End-of-life risk: Ruby 3.2 and older branches will receive no patches, forcing teams on legacy versions to complete a full branch migration rather than a quick point release.
- Downstream software: Veria Labs identified vulnerable bundled Ruby runtimes inside specific versions of GitLab, GitHub Enterprise Server, Mastodon, OpenProject, Discourse, and Chatwoot.
- Remediation steps: Administrators should prioritize internet-facing services that compile user-supplied regular expressions or perform case conversions on untrusted input, rebuild container images, and restart background workers to load the patched interpreter.
For self-managed applications, update to the fixed release for your branch, rebuild any affected images, and redeploy the web processes and background workers that use them. Verify the Ruby version inside the running deployment.
For products that ship their own Ruby runtime, check the vendor’s update guidance, since updating the host’s Ruby package can leave the bundled copy untouched.
Ruby 3.2 and earlier are end of life and won’t receive these fixes from the Ruby project. Track those deployments as migrations to a supported branch or vendor-supported release.
Other news: Wiz launched an AI Security Agent that analyzes application code and cloud permissions to uncover AI agents missing from enterprise inventories and flag potential paths to sensitive data.





