Back to vendor advisories
Ubuntu Security NoticesUSN-9176-1

USN-9176-1: Ruby vulnerabilities

Severity not listed 0 CVEs Published Nov 19, 2026 at 8:07 PM UTC

Summary

Stephan Lipp discovered that Ruby incorrectly handled converting the case of certain strings. An attacker could possibly use this issue to cause a denial of service or execute arbitrary code. (GHSA-34m4-m9fh-gqp5)

Owais Lone discovered that Ruby incorrectly handled compiling certain large regular expressions. An attacker could possibly use this issue to cause a denial of service or execute arbitrary code. (GHSA-3p8q-wmhx-vm2w)

Stephan Lipp discovered that Ruby incorrectly handled converting certain regular expressions to strings. An attacker could possibly use this issue to cause a denial of service or execute arbitrary code. (GHSA-7whj- cfh7-xgm4)

Stephan Lipp discovered that Ruby incorrectly handled memory when parsing certain regular expressions. An attacker could possibly use this issue to cause a denial of service or execute arbitrary code. (GHSA-7x2q-68qv-6p8x)

It was discovered that Ruby incorrectly handled converting the case of certain large strings. An attacker could possibly use this issue to cause a denial of service or execute arbitrary code. (GHSA-87fm-7w84-j2px)

It was discovered that Ruby incorrectly handled certain case-insensitive regular expressions. An attacker could possibly use this issue to cause a denial of service or obtain sensitive information. (GHSA-pvgc-g7gj-pv6h)

Stephan Lipp discovered that Ruby incorrectly handled certain case- insensitive regular expressions. An attacker could possibly use this issue to cause a denial of service or obtain sensitive information. (GHSA- wpqw-5qxg-m68r)

Products covered

A separate affected-products list was not included in the collected bulletin.

Remediation

Separate remediation guidance was not included in the collected bulletin.

CVEs in this advisory 0

No CVE identifiers were listed in the collected bulletin.

Updates

  1. Published by Ubuntu

    The publication date reported by the vendor.

  2. Added to SecurityAlert

    We collected the advisory from the official source.

  3. Confirmed at the source

    Our collector saw this advisory during a later source check.