Ruby · Ruby · published 2026-08-27
CVE-2026-80213
Routine No exploitation evidence; EPSS 0.3%.
CVE-2026-80213 is not known to be exploited in the wild. EPSS estimates a 0.3% chance of exploitation in the next 30 days, higher than 19% of all CVEs. This Ruby vulnerability: CVSS 4.0 (v3.1). Fixed upstream in Ruby 4.0.9, 3.4.12, 3.3.13; patched packages are out for Debian; Debian and Red Hat Enterprise Linux still have unfixed releases. Routine: patch when convenient.
Jump to: Remediation Exploit intelAffected versionsDescription
Remediation#
Fixed upstream in Ruby 4.0.9, 3.4.12, 3.3.13.
Linux distribution packages
If you run the distro’s package rather than an upstream build, this is the version to look for.
| Distro | Release | Package | Status |
|---|---|---|---|
| Debian | 13 trixie | ruby3.3 | Fixed in 3.3.13-0+deb13u1 |
| 12 bookworm | ruby3.1 | No fix yet | |
| Red Hat Enterprise Linux (+4 more packages) | RHEL 10 | ruby | No fix yet |
| RHEL 10 | ruby-33 | No fix yet | |
| RHEL 10 | ruby-40 | No fix yet | |
| RHEL 10 | ruby4.0 | No fix yet | |
| RHEL 9 | ruby | No fix yet | |
| RHEL 9 | ruby-30 | No fix yet | |
| RHEL 9 | ruby-33 | No fix yet | |
| RHEL 9 | ruby-40 | No fix yet |
From the Debian Security Tracker, Ubuntu security notices (CC BY-SA 4.0) and Red Hat Security Data (CC BY 4.0). Check the distro link before acting.
Patch events
Language runtimeRuby
Ruby security releases: 4.0.9, 3.4.12, 3.3.13
Upgrade to
4.0.93.4.123.3.13Why: CVE-2026-97229: Known exploited (CISA KEV) and CISA requires forensic triage: patch and check for compromise.
Exploit intelligence#
| Signal | Value | Source |
|---|---|---|
| Known exploited | No | CISA KEV |
| Ransomware use | — | CISA KEV |
| EPSS (30-day exploitation probability) | 0.3% (20th pct) | FIRST EPSS v2026.06.15 |
| CVSS base score | 4.0 (v3.1)CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:N/I:L/A:N | CNA / CISA ADP |
| SSVC exploitation | none | CISA Vulnrichment |
| SSVC automatable | No | CISA Vulnrichment |
| SSVC technical impact | partial | CISA Vulnrichment |
Affected versions (from the CVE record)#
- Ruby resolv
0to before0.3.2(affected)0.4.0to before0.7.2(affected)
Description (from the CVE record)#
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.
Quoted from the CVE Program record.