An update for ruby is now available for openEuler-24.03-LTS-SP3 Security Advisory openeuler-security@openeuler.org openEuler security committee openEuler-SA-2026-3868 Final 1.0 1.0 2026-09-14 Initial 2026-09-14 2026-09-14 openEuler SA Tool V1.0 2026-09-14 ruby security update An update for ruby is now available for openEuler-24.03-LTS-SP3 Ruby is a fast and easy interpreted scripting language for object-oriented programming. It has many functions for processing text Files and perform system management tasks (such as Perl). Security Fix(es): An issue was discovered in the resolv gem before 0.7.2 for Ruby. Resolv::DNS::MessageEncoder wrote a DNS label'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("C", 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'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) An update for ruby is now available for openEuler-24.03-LTS-SP3. openEuler Security has rated this update as having a security impact of medium. A Common Vunlnerability Scoring System(CVSS)base score,which gives a detailed severity rating, is available for each vulnerability from the CVElink(s) in the References section. Medium ruby https://www.openeuler.org/zh/security/security-bulletins/detail/?id=openEuler-SA-2026-3868 https://www.openeuler.org/en/security/cve/detail/?cveId=CVE-2026-80213 https://nvd.nist.gov/vuln/detail/CVE-2026-80213 openEuler-24.03-LTS-SP3 ruby-3.2.2-161.oe2403sp3.aarch64.rpm ruby-bundled-gems-3.2.2-161.oe2403sp3.aarch64.rpm ruby-debuginfo-3.2.2-161.oe2403sp3.aarch64.rpm ruby-debugsource-3.2.2-161.oe2403sp3.aarch64.rpm ruby-devel-3.2.2-161.oe2403sp3.aarch64.rpm rubygem-bigdecimal-3.1.3-161.oe2403sp3.aarch64.rpm rubygem-io-console-0.6.0-161.oe2403sp3.aarch64.rpm rubygem-json-2.6.3-161.oe2403sp3.aarch64.rpm rubygem-openssl-3.1.0-161.oe2403sp3.aarch64.rpm rubygem-psych-5.0.1-161.oe2403sp3.aarch64.rpm rubygem-rbs-2.8.2-161.oe2403sp3.aarch64.rpm ruby-3.2.2-161.oe2403sp3.src.rpm ruby-3.2.2-161.oe2403sp3.x86_64.rpm ruby-bundled-gems-3.2.2-161.oe2403sp3.x86_64.rpm ruby-debuginfo-3.2.2-161.oe2403sp3.x86_64.rpm ruby-debugsource-3.2.2-161.oe2403sp3.x86_64.rpm ruby-devel-3.2.2-161.oe2403sp3.x86_64.rpm rubygem-bigdecimal-3.1.3-161.oe2403sp3.x86_64.rpm rubygem-io-console-0.6.0-161.oe2403sp3.x86_64.rpm rubygem-json-2.6.3-161.oe2403sp3.x86_64.rpm rubygem-openssl-3.1.0-161.oe2403sp3.x86_64.rpm rubygem-psych-5.0.1-161.oe2403sp3.x86_64.rpm rubygem-rbs-2.8.2-161.oe2403sp3.x86_64.rpm ruby-help-3.2.2-161.oe2403sp3.noarch.rpm ruby-irb-3.2.2-161.oe2403sp3.noarch.rpm rubygem-did_you_mean-1.6.3-161.oe2403sp3.noarch.rpm rubygem-minitest-5.16.3-161.oe2403sp3.noarch.rpm rubygem-rake-13.0.6-161.oe2403sp3.noarch.rpm rubygem-rdoc-6.5.0-161.oe2403sp3.noarch.rpm rubygem-rexml-3.2.5-161.oe2403sp3.noarch.rpm rubygem-rss-0.2.9-161.oe2403sp3.noarch.rpm rubygem-test-unit-3.5.7-161.oe2403sp3.noarch.rpm rubygem-typeprof-0.21.3-161.oe2403sp3.noarch.rpm rubygems-3.4.10-161.oe2403sp3.noarch.rpm rubygems-devel-3.4.10-161.oe2403sp3.noarch.rpm An issue was discovered in the resolv gem before 0.7.2 for Ruby. Resolv::DNS::MessageEncoder wrote a DNS label'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("C", 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'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. 2026-09-14 CVE-2026-80213 openEuler-24.03-LTS-SP3 Medium 4.0 AV:N/AC:H/PR:N/UI:N/S:C/C:N/I:L/A:N ruby security update 2026-09-14 https://www.openeuler.org/zh/security/security-bulletins/detail/?id=openEuler-SA-2026-3868