CVE-2026-97229

Description

A flaw was found in Ruby. When compiling a specially crafted regular expression with the methods Regexp.new, Regexp.union, Regexp.compile, or via a string interpolation such as /#{input}/, an integer overflow in the size of the compiled pattern can occur. This integer overflow causes memory corruption, potentially resulting in arbitrary code execution.

Statement

Red Hat has rated the impact of these flaws as Moderate for the Ruby packages shipped in Red Hat Enterprise Linux. The Ruby packages provide a language interpreter and standard library and do not accept external input on their own; these flaws are reachable only when an application compiles a regular expression constructed from attacker-controlled input.

On 2026-11-17, Ruby published a security advisory in the ruby/ruby repository for each of the three underlying bugs and requested CVE identifiers for them; CVE-2026-97229 is covered by GHSA-22mf-ggw7-pxfx. While Ruby has generally considered it unsafe to compile a regular expression created from untrusted input, it has decided that "memory corruption reachable by compiling an untrusted pattern is a vulnerability in Ruby". At the same time, Ruby continues to scope reachability narrowly, stating that the flaws "are reached only when an application compiles a regular expression from a string that an attacker controls, for example by passing it to Regexp.new, Regexp.union or Regexp.compile", and that "applications that only use regular expressions written by their own developers are not affected".

Mitigation

To mitigate this vulnerability, do not compile regular expressions from untrusted sources. Standard safeguards such as Regexp.timeout or limiting the length of the input pattern do not protect against this issue.

Common Vulnerability Scoring System (CVSS) Score Details

Info alert:Important note

CVSS scores for open source components depend on vendor-specific factors (e.g. version or build chain). Therefore, Red Hat's score and impact rating can be different from NVD and other vendors. Red Hat remains the authoritative CVE Naming Authority (CNA) source for its products and services (see Red Hat classifications).

CVSS v3 Score Breakdown

Red HatNVDcve.org
Base Score9.8N/A10
Attack VectorNetworkN/ANetwork
Attack ComplexityLowN/ALow
Privileges RequiredNoneN/ANone
User InteractionNoneN/ANone
ScopeUnchangedN/AChanged
ConfidentialityHighN/AHigh
Integrity ImpactHighN/AHigh
Availability ImpactHighN/AHigh

Vector

Red Hat: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

cve.org: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H

Understanding the Weakness (CWE)

Availability

Technical Impact: DoS: Crash, Exit, or Restart; DoS: Resource Consumption (Memory); DoS: Instability

This weakness can generally lead to undefined behavior and therefore crashes. When the calculated result is used for resource allocation, this weakness can cause too many (or too few) resources to be allocated, possibly enabling crashes if the product requests more resources than can be provided. If the calculated result involves time values, then the product might crash when it encounters a time that is less than the previously-calculated time.

Integrity

Technical Impact: Modify Memory

If the value in question is important to data (as opposed to flow), simple data corruption has occurred. Also, if the overflow/wraparound results in other conditions such as buffer overflows, further memory corruption may occur.

Confidentiality,Availability,Access Control

Technical Impact: Execute Unauthorized Code or Commands; Bypass Protection Mechanism

This weakness can sometimes trigger buffer overflows, which can be used to execute arbitrary code. This is usually outside the scope of the product's implicit security policy.

Availability,Other

Technical Impact: Alter Execution Logic; DoS: Crash, Exit, or Restart; DoS: Resource Consumption (CPU)

If the overflow/wraparound occurs in a loop index variable, this could cause the loop to terminate at the wrong time - too early, too late, or not at all (i.e., infinite loops). With too many iterations, some loops could consume too many resources such as memory, file handles, etc., possibly leading to a crash or other DoS.

Access Control

Technical Impact: Bypass Protection Mechanism

If integer values are used in security-critical decisions, such as calculating quotas or allocation limits, integer overflows can be used to cause an incorrect security decision.

Access Control

Technical Impact: Bypass Protection Mechanism; DoS: Crash, Exit, or Restart

If integer values are used in time-based, security-critical decisions, such as calculating expiration times or determining whether an event occurs within a specific time or date range, to cause an incorrect security decision. The consequences could even include "self-DoS" if the overflow produces a time value that is not accounted for in protection mechanism logic [REF-1570].

Frequently Asked Questions

Want to get errata notifications? Sign up here.