<?xml version="1.0" encoding="utf-8"?>
  <?xml-stylesheet type="text/xsl" href="sa-render.xsl"?>
  <update from="huaweicloud.com" type="security" status="stable" version="1">
    <id>HCE3-SA-2026-0493</id>
    <title>An update for ruby is now available for HCE 3.0</title>
    <severity>Critical</severity>
    <release>HCE 3.0</release>
    <issued date="2026-10-23 07:34:06"/>
    <updated date="2026-10-23 07:34:06"/>
    <references>
      <reference href="https://nvd.nist.gov/vuln/detail/CVE-2026-47241" id="CVE-2026-47241" title="CVE-2026-47241 Base Score: 4.3 Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L" type="cve"/>
      <reference href="https://nvd.nist.gov/vuln/detail/CVE-2026-80212" id="CVE-2026-80212" title="CVE-2026-80212 Base Score: 7.5 Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H" type="cve"/>
      <reference href="https://nvd.nist.gov/vuln/detail/CVE-2026-47240" id="CVE-2026-47240" title="CVE-2026-47240 Base Score: 6.5 Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:L" type="cve"/>
      <reference href="https://nvd.nist.gov/vuln/detail/CVE-2026-47242" id="CVE-2026-47242" title="CVE-2026-47242 Base Score: 6.8 Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:L" type="cve"/>
      <reference href="https://nvd.nist.gov/vuln/detail/CVE-2026-82455" id="CVE-2026-82455" title="CVE-2026-82455 Base Score: 7.1 Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:H" type="cve"/>
      <reference href="https://nvd.nist.gov/vuln/detail/CVE-2026-80213" id="CVE-2026-80213" title="CVE-2026-80213 Base Score: 4.0 Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:N/I:L/A:N" type="cve"/>
      <reference href="https://nvd.nist.gov/vuln/detail/CVE-2026-27820" id="CVE-2026-27820" title="CVE-2026-27820 Base Score: 9.8 Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H" type="cve"/>
      <reference href="https://nvd.nist.gov/vuln/detail/CVE-2025-24294" id="CVE-2025-24294" title="CVE-2025-24294 Base Score: 7.5 Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H" type="cve"/>
    </references>
    <description>Security Fix(es):

Net::IMAP implements Internet Message Access Protocol (IMAP) client functionality in Ruby. Prior to 0.6.5 and 0.5.15, several Net::IMAP commands accept a raw string argument which is only validated to prevent CRLF injection and then sent verbatim. If this string is derived from user-controlled input, an attacker can force the next command to be absorbed as a continuation of the first command. This will cause the first command to eventually fail, but also prevents it from returning until another command is sent (from another thread). That other command will not return until the connection is closed. This vulnerability is fixed in 0.6.5 and 0.5.15. (CVE-2026-47241)

An issue was discovered in the resolv gem before 0.7.2 for Ruby. Resolv::DNS::Resource.get_class, Resolv::DNS::Resource::Generic.create, and Resolv::DNS::SvcParam::Generic.create generate a new class for each unknown DNS resource record (type, class) pair, or each unknown SvcParamKey, encountered while decoding a response. Each generated class was permanently registered both as a constant on Resource (or SvcParam::Generic) and as an entry in a class-lookup hash (ClassHash), and thus the class remained reachable through that constant after the response was discarded. Type and class are each 16-bit values, and thus an attacker controlling DNS responses (a spoofed response, or a malicious or hijacked upstream DNS server) has roughly 2^32 distinct (type, class) pairs to choose from. A single response of a few hundred kilobytes carrying tens of thousands of distinct unknown types permanently grows process memory by tens of megabytes; repeated responses accumulate without bound and are never reclaimed by garbage collection, because the constant keeps each class alive. Any code path that calls Resolv::DNS::Message.decode on attacker-influenced DNS responses is affected. resolv is a default gem, and thus this is reachable from a plain Ruby installation without any additional dependency. (CVE-2026-80212)

Net::IMAP implements Internet Message Access Protocol (IMAP) client functionality in Ruby. Prior to 0.6.5 and 0.5.15, several Net::IMAP commands accept a &quot;raw data&quot; argument that is sent verbatim after validation to prevent command injection. However, if a server does not support non-synchronizing literals, it may still be possible to inject arbitrary IMAP commands inside non-synchronizing literals.  A server without support for non-synchronizing literals may interpret the &quot;+}\r\n&quot; as the end of a malformed command line and respond with a tagged BAD. In that case, the contents of the literal will be interpreted as one or more new pipelined commands, allowing a CRLF command injection attack to succeed. This affects criteria for #search and #uid_search; search_keys for #sort, #thread, #uid_sort, and #uid_thread; and attr for #fetch and #uid_fetch. This vulnerability is fixed in 0.6.5 and 0.5.15. (CVE-2026-47240)

Net::IMAP implements Internet Message Access Protocol (IMAP) client functionality in Ruby. Prior to 0.6.5 and 0.5.15, when Net::IMAP#id is called with a hash argument, although the ID field value strings are correctly quoted (escaping quoted specials), they were not validated to prohibit CRLF sequences. While Net::IMAP#enable does process its arguments for aliases, it does not validate them as valid atoms (or as a list of valid atoms). The #to_s value is sent verbatim. Arguments to either command could be used by an attacker to inject arbitrary IMAP commands. This vulnerability is fixed in 0.6.5 and 0.5.15. (CVE-2026-47242)

REJECTED Rejected reason: The RubyGems maintainers determined that the reported symlink-following behavior during gem extraction is not a security vulnerability, so no vulnerability exists for this record to describe. (CVE-2026-82455)

An issue was discovered in the resolv gem before 0.7.2 for Ruby. Resolv::DNS::MessageEncoder wrote a DNS label_x27;s length into a single octet without checking its range. A label longer than 255 octets had its length stored modulo 256 but the label data was written unchanged, and thus the bytes on the wire described a different name than the one the application asked to encode. RFC 1035 section 2.3.4 limits a label to 63 octets, and the two high bits of the length octet are reserved for compression pointers. put_string packed the length with put_pack(&quot;C&quot;, d.length) and put_label used it for labels, and thus any value from 0 to 255 could end up as a label length octet, including the reserved 0x40-0xBF range and the 0xC0-0xFF pointer range. Resolv::DNS::Name.create did not check per-label or total name length either, and thus an attacker-controlled hostname reached the encoder unchanged. An application that resolves an attacker-controlled hostname sends a query whose wire bytes name a domain the attacker chose. A hostname suffix that the application validates against an allowlist becomes padding that never appears on the wire, and thus allowlist and egress checks can be bypassed. The recursive resolver caches the response under the attacker_x27;s name, and DNS logs record that name rather than the one the application asked for. A label length whose low octet lands in the 0xC0-0xFF range produces a length octet that conforming parsers read as the start of a compression pointer, with the following attacker-controlled byte as the offset. (CVE-2026-80213)

zlib is a Ruby interface for the zlib compression/decompression library. Versions 3.0.0 and below, 3.1.0, 3.1.1, 3.2.0 and 3.2.1 contain a buffer overflow vulnerability in the Zlib::GzipReader. The zstream_buffer_ungets function prepends caller-provided bytes ahead of previously produced output but fails to guarantee the backing Ruby string has enough capacity before the memmove shifts the existing data. This can lead to memory corruption when the buffer length exceeds capacity. This issue has been fixed in versions 3.0.1, 3.1.2 and 3.2.3. (CVE-2026-27820)

The attack vector is a potential Denial of Service (DoS). The vulnerability is caused by an insufficient check on the length of a decompressed domain name within a DNS packet.

An attacker can craft a malicious DNS packet containing a highly compressed domain name. When the resolv library parses such a packet, the name decompression process consumes a large amount of CPU resources, as the library does not limit the resulting length of the name.

This resource consumption can cause the application thread to become unresponsive, resulting in a Denial of Service condition. (CVE-2025-24294)
</description>
    <pkglist>
      <collection short="HCE 3.0" package="ruby">
        <name>HCE 3.0</name>
        <package arch="noarch" name="rubygems" version="3.4.10" release="147.r14.hce3">
          <filename>rubygems-3.4.10-147.r14.hce3.noarch.rpm</filename>
        </package>
        <package arch="noarch" name="rubygems-devel" version="3.4.10" release="147.r14.hce3">
          <filename>rubygems-devel-3.4.10-147.r14.hce3.noarch.rpm</filename>
        </package>
        <package arch="x86_64" name="rubygem-bigdecimal" version="3.1.3" release="147.r14.hce3">
          <filename>rubygem-bigdecimal-3.1.3-147.r14.hce3.x86_64.rpm</filename>
        </package>
        <package arch="noarch" name="rubygem-did_you_mean" version="1.6.3" release="147.r14.hce3">
          <filename>rubygem-did_you_mean-1.6.3-147.r14.hce3.noarch.rpm</filename>
        </package>
        <package arch="x86_64" name="rubygem-io-console" version="0.6.0" release="147.r14.hce3">
          <filename>rubygem-io-console-0.6.0-147.r14.hce3.x86_64.rpm</filename>
        </package>
        <package arch="x86_64" name="rubygem-json" version="2.6.3" release="147.r14.hce3">
          <filename>rubygem-json-2.6.3-147.r14.hce3.x86_64.rpm</filename>
        </package>
        <package arch="noarch" name="rubygem-minitest" version="5.16.3" release="147.r14.hce3">
          <filename>rubygem-minitest-5.16.3-147.r14.hce3.noarch.rpm</filename>
        </package>
        <package arch="x86_64" name="rubygem-openssl" version="3.1.0" release="147.r14.hce3">
          <filename>rubygem-openssl-3.1.0-147.r14.hce3.x86_64.rpm</filename>
        </package>
        <package arch="x86_64" name="rubygem-psych" version="5.0.1" release="147.r14.hce3">
          <filename>rubygem-psych-5.0.1-147.r14.hce3.x86_64.rpm</filename>
        </package>
        <package arch="noarch" name="rubygem-rake" version="13.0.6" release="147.r14.hce3">
          <filename>rubygem-rake-13.0.6-147.r14.hce3.noarch.rpm</filename>
        </package>
        <package arch="x86_64" name="rubygem-rbs" version="2.8.2" release="147.r14.hce3">
          <filename>rubygem-rbs-2.8.2-147.r14.hce3.x86_64.rpm</filename>
        </package>
        <package arch="noarch" name="rubygem-rdoc" version="6.5.0" release="147.r14.hce3">
          <filename>rubygem-rdoc-6.5.0-147.r14.hce3.noarch.rpm</filename>
        </package>
        <package arch="noarch" name="rubygem-rexml" version="3.2.5" release="147.r14.hce3">
          <filename>rubygem-rexml-3.2.5-147.r14.hce3.noarch.rpm</filename>
        </package>
        <package arch="noarch" name="rubygem-rss" version="0.2.9" release="147.r14.hce3">
          <filename>rubygem-rss-0.2.9-147.r14.hce3.noarch.rpm</filename>
        </package>
        <package arch="noarch" name="rubygem-test-unit" version="3.5.7" release="147.r14.hce3">
          <filename>rubygem-test-unit-3.5.7-147.r14.hce3.noarch.rpm</filename>
        </package>
        <package arch="noarch" name="rubygem-typeprof" version="0.21.3" release="147.r14.hce3">
          <filename>rubygem-typeprof-0.21.3-147.r14.hce3.noarch.rpm</filename>
        </package>
        <package arch="x86_64" name="ruby" version="3.2.2" release="147.r14.hce3">
          <filename>ruby-3.2.2-147.r14.hce3.x86_64.rpm</filename>
        </package>
        <package arch="x86_64" name="ruby-bundled-gems" version="3.2.2" release="147.r14.hce3">
          <filename>ruby-bundled-gems-3.2.2-147.r14.hce3.x86_64.rpm</filename>
        </package>
        <package arch="x86_64" name="ruby-devel" version="3.2.2" release="147.r14.hce3">
          <filename>ruby-devel-3.2.2-147.r14.hce3.x86_64.rpm</filename>
        </package>
        <package arch="noarch" name="ruby-help" version="3.2.2" release="147.r14.hce3">
          <filename>ruby-help-3.2.2-147.r14.hce3.noarch.rpm</filename>
        </package>
        <package arch="noarch" name="ruby-irb" version="3.2.2" release="147.r14.hce3">
          <filename>ruby-irb-3.2.2-147.r14.hce3.noarch.rpm</filename>
        </package>
        <package arch="aarch64" name="rubygem-bigdecimal" version="3.1.3" release="147.r14.hce3">
          <filename>rubygem-bigdecimal-3.1.3-147.r14.hce3.aarch64.rpm</filename>
        </package>
        <package arch="aarch64" name="rubygem-io-console" version="0.6.0" release="147.r14.hce3">
          <filename>rubygem-io-console-0.6.0-147.r14.hce3.aarch64.rpm</filename>
        </package>
        <package arch="aarch64" name="rubygem-json" version="2.6.3" release="147.r14.hce3">
          <filename>rubygem-json-2.6.3-147.r14.hce3.aarch64.rpm</filename>
        </package>
        <package arch="aarch64" name="rubygem-openssl" version="3.1.0" release="147.r14.hce3">
          <filename>rubygem-openssl-3.1.0-147.r14.hce3.aarch64.rpm</filename>
        </package>
        <package arch="aarch64" name="rubygem-psych" version="5.0.1" release="147.r14.hce3">
          <filename>rubygem-psych-5.0.1-147.r14.hce3.aarch64.rpm</filename>
        </package>
        <package arch="aarch64" name="rubygem-rbs" version="2.8.2" release="147.r14.hce3">
          <filename>rubygem-rbs-2.8.2-147.r14.hce3.aarch64.rpm</filename>
        </package>
        <package arch="aarch64" name="ruby" version="3.2.2" release="147.r14.hce3">
          <filename>ruby-3.2.2-147.r14.hce3.aarch64.rpm</filename>
        </package>
        <package arch="aarch64" name="ruby-bundled-gems" version="3.2.2" release="147.r14.hce3">
          <filename>ruby-bundled-gems-3.2.2-147.r14.hce3.aarch64.rpm</filename>
        </package>
        <package arch="aarch64" name="ruby-devel" version="3.2.2" release="147.r14.hce3">
          <filename>ruby-devel-3.2.2-147.r14.hce3.aarch64.rpm</filename>
        </package>
      </collection>
    </pkglist>
  </update>
