Ruby · Ruby · published 2026-08-27
CVE-2026-80212
Routine No exploitation evidence; EPSS 0.4%.
CVE-2026-80212 is not known to be exploited in the wild. EPSS estimates a 0.4% chance of exploitation in the next 30 days, higher than 35% of all CVEs. This Ruby vulnerability: CVSS 7.5 (v3.1), attacks can be automated. Fixed upstream in Ruby 4.0.9, 3.4.12, 3.3.13; patched packages are out for Debian and Red Hat Enterprise Linux; Debian still has 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 | RHEL 10 | ruby | Fixed in 3.3.12-15.el10_2 RHSA-2026:72785 |
| RHEL 10 | ruby4.0 | Fixed in 4.0.6-37.el10_2 RHSA-2026:72427 | |
| RHEL 9 | ruby | Fixed in 3.0.7-168.el9_8 RHSA-2026:72286 | |
| RHEL 6 | ruby | Won’t fix |
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.4% (35th pct) | FIRST EPSS v2026.06.15 |
| CVSS base score | 7.5 (v3.1)CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | CNA / CISA ADP |
| SSVC exploitation | none | CISA Vulnrichment |
| SSVC automatable | Yes | 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::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.
Quoted from the CVE Program record.