Ruby Regexp and String flaws span seven advisories published on November 18, 2026. Ruby fixed them in 3.3.14, 3.4.13 and 4.0.10. Its advisory says proof of concepts show that some flaws can produce remote code execution in certain scenarios.
The important split is the application path into each bug. Two flaws involve changing a string’s case. Five involve regular expressions, but their triggers and possible outcomes differ.
The matrix below helps teams identify the relevant path before they review exposure. Compare verified advisories with your runtime inventory, then use a vulnerability intelligence platform to prioritize remediation.
Ruby Regexp and String Flaws: Which Path Reaches Each Bug?
| Ruby advisory | Trigger and flaw | Possible impact Ruby states |
|---|---|---|
| GHSA-34m4-m9fh-gqp5 | Case conversion of a crafted string; one-byte heap buffer overflow | RCE in some scenarios; Ruby reports a supporting PoC |
| GHSA-87fm-7w84-j2px | Case conversion whose result exceeds 4 GiB; integer overflow and heap buffer overflow | RCE in some scenarios; Ruby reports a supporting PoC |
| GHSA-7x2q-68qv-6p8x | Compile an attacker-controlled Regexp pattern; double free | RCE in some scenarios; Ruby reports a supporting PoC |
| GHSA-3p8q-wmhx-vm2w | Compile an attacker-controlled Regexp pattern; integer overflow and heap buffer overflow | RCE in some scenarios; Ruby reports a supporting PoC |
| GHSA-wpqw-5qxg-m68r | Use an attacker-controlled pattern in case-insensitive matching; out-of-bounds read | Possible RCE; Ruby’s PoC demonstrates attacker-controlled memory corruption |
| GHSA-7whj-cfh7-xgm4 | Convert a crafted Regexp to a string after compiling attacker-controlled patterns; heap buffer overflow | Information disclosure or RCE; Ruby reports a supporting RCE PoC |
| GHSA-pvgc-g7gj-pv6h | Match a crafted string with a case-insensitive backreference; out-of-bounds read | Possible memory disclosure or process crash |
Every row uses Ruby’s stated possibility, not a claim about attacks in the wild. A PoC shows technical feasibility under its tested conditions. It does not show that the same result follows whenever an application receives user input.
Where Are the Two String Case-Conversion Risks?
The first case-conversion issue writes one byte beyond a heap buffer. Ruby’s remote code execution definition explains the outcome, but this advisory describes it as conditional. Ruby’s separate GHSA says single-byte encodings such as ISO-8859-1 and Windows-1252 are relevant.
The second issue starts with an integer overflow when the converted output exceeds 4 GiB. That can lead to a heap buffer overflow. The size condition matters when prioritizing realistic application paths; it does not narrow Ruby’s patch recommendation.
Only the first issue has the confirmed identifier CVE-2026-132825 in the CNA record. Ruby’s seven-part announcement still lists GHSA identifiers while CVEs are pending. Treat the other six GHSA identifiers as their current references, without assigning them the first flaw’s CVE.
How Do the Five Regexp Conditions Differ?
Two defects arise while Ruby compiles a pattern supplied by an attacker. One can free the same buffer twice while parsing a character-class intersection. The other can overflow a compiled-program size calculation and then write beyond a heap buffer.
Another issue affects case-insensitive matching with an attacker-controlled pattern. Ruby says an out-of-bounds read can cause attacker-controlled memory corruption. Its PoC statement supports that corruption; the advisory describes RCE as a possibility, not a demonstrated result for that particular PoC.
A fourth path appears when an application converts a crafted Regexp to a string. Ruby says this heap overflow can disclose information or permit RCE where attacker-controlled patterns are compiled. This condition is distinct from merely matching ordinary user text against a fixed pattern.
The final path involves case-insensitive backreference matching against a crafted subject string. Ruby describes potential memory disclosure or a crash, without adding RCE to this row’s impact. A review that groups all five Regexp flaws as equivalent would miss that difference.
Which Ruby Versions Need an Upgrade?
Ruby lists 3.3.13 and earlier, 3.4.0 through 3.4.12, and 4.0.0 through 4.0.9 as affected. Its fixed releases are 3.3.14, 3.4.13 and 4.0.10. The 3.3 branch is in security maintenance, while 3.2 and earlier are end of life and will not receive these fixes.
Inventory the Ruby version actually loaded by each deployed process and build worker. A package manifest can differ from the running interpreter after a container or host update. Use a vulnerability management workflow to record the affected runtimes, owners and completion evidence.
- InventoryRecord active Ruby versions in services, workers and build images.
- TraceIdentify untrusted strings that reach case conversion or Regexp construction and matching.
- UpgradeMove each supported branch to 3.3.14, 3.4.13 or 4.0.10.
- VerifyRestart affected processes and confirm their loaded interpreter version.
The checklist is our operational reading of Ruby’s triggers and patch guidance. Prioritize applications that turn untrusted data into patterns, then inspect case-conversion paths and the other matching conditions. Keep the vendor’s broad upgrade recommendation for the entire affected release range.
How Should Teams Interpret the Ruby PoCs?
Ruby reports PoCs for six of the seven issues, with a narrower memory-corruption demonstration for GHSA-wpqw-5qxg-m68r. That evidence is separate from confirmed exploitation in a deployed application. A dated CISA KEV lookup for catalog version 2026.11.18 did not list CVE-2026-132825.
Brandefense Blackhole counted one dark-chat post mentioning CVE-2026-132825 from August 21 through November 19, 2026. The measured unit is posts, not incidents or unique actors. This count does not establish exploitation, and the window includes time before the CVE record appeared.
The CNA record assigns CVE-2026-132825 a CVSS 3.1 score of 7.4 High with a local attack vector and high attack complexity. Ruby’s GHSA calls that case-conversion issue Critical. These are different source assessments; neither turns a conditional remote outcome into a confirmed attack.
Review crash and memory-fault telemetry around affected Ruby processes as an investigative step, then connect findings to the actual data path. The advisories do not supply a detection signature. Patch tracking should therefore use the loaded version and application exposure, not a single alert rule.
The direct fix remains Ruby’s patched release for the branch in use. Confirm the running version after rollout and retain the application-path review for residual exposure assessment.
Frequently Asked Questions
Does every Ruby Regexp flaw allow remote code execution?
Ruby describes possible RCE for several paths. Its case-insensitive backreference advisory instead describes possible memory disclosure or a process crash.
Which Ruby releases contain the fixes?
Ruby recommends 3.3.14, 3.4.13 or 4.0.10, depending on the branch. Version 3.2 and earlier will not receive these fixes.
Does a Ruby PoC prove active exploitation?
A PoC demonstrates technical behavior in tested conditions. It does not establish an incident or exploitation in a deployed application.
Sources
- Ruby, Security Advisories: Multiple Vulnerabilities in Regexp and String Case Conversion, November 18, 2026
- CVE Program, CVE-2026-132825 CNA Record, November 19, 2026
- Ruby Security Advisory GHSA-7x2q-68qv-6p8x
- Ruby Security Advisory GHSA-87fm-7w84-j2px
- Ruby Security Advisory GHSA-wpqw-5qxg-m68r
- Ruby Security Advisory GHSA-3p8q-wmhx-vm2w
- Ruby Security Advisory GHSA-7whj-cfh7-xgm4
- Ruby Security Advisory GHSA-pvgc-g7gj-pv6h
