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
Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-08-27. a secondary CVSS source baseline 7.5; sources differ by 0.0.
- High severity, but no confirmed exploitation yet
A fix is available — apply it.
- CVSS v3
- 7.5
- EG Score
- 7.5(high)
- EG Risk
- 49(Track)EG Risk 49/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity75% × 45%Exploitation1% × 40%Automatability100% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 1%
- EPSS %ILE
- 46%
- KEV
- Not listed
Published
August 27, 2026
Last Modified
September 9, 2026
Advisory Details (2)
Auto-updated Aug 27, 2026Security advisories: CVE-2026-80212 and CVE-2026-80213 | Ruby
https://www.ruby-lang.org/en/news/2026/08/27/multiple-vulnerabilities-in-resolv/GitHub - ruby/resolv: A thread-aware DNS resolver library written in Ruby · GitHub
https://github.com/ruby/resolvVendor Advisories for CVE-2026-80212(6)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
- RHSA-2026:62563Red Hat Product SecurityHigh
Red Hat Security Advisory: Red Hat Hardened Images RPMs Security Update
- RHSA-2026:62562Red Hat Product SecurityHigh
Red Hat Security Advisory: Red Hat Hardened Images RPMs Security Update
- GHSA-x2vh-ff4w-v64cGitHub Security AdvisoriesHigh
An issue was discovered in the resolv gem before 0.7.2 for Ruby. Resolv::DNS::Resource.get_class,...
- RHSA-2026:57994Red Hat Product SecurityHigh
Red Hat Security Advisory: Red Hat Hardened Images RPMs bug fix and enhancement update
- RHSA-2026:57986Red Hat Product SecurityHigh
Red Hat Security Advisory: Red Hat Hardened Images RPMs bug fix and enhancement update
- RHSA-2026:57565Red Hat Product SecurityHigh
Red Hat Security Advisory: Red Hat Hardened Images RPMs Security Update
Patch Availability(5)
| Vendor / Ecosystem | Fixed in / Patch | Released | Source |
|---|---|---|---|
| redhat | ruby3-3-main-3.3.10-23.6.hum1 | 2026-09-02 | redhat |
| redhat | ruby4-0-main-4.0.6-37.3.hum1 | 2026-09-02 | redhat |
| redhat | ruby3-4-main-3.4.10-31.6.hum1 | 2026-08-21 | redhat |
| redhat | ruby3-3-main-3.3.10-23.5.hum1 | 2026-08-21 | redhat |
| redhat | ruby4-0-main-4.0.6-37.2.hum1 | 2026-08-20 | redhat |
Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 39× in last 7d / 122× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
Showing the most recent 100 of 122 total refreshes for this CVE.
- 2026-09-18 22:58 UTCEG score recompute
- 2026-09-18 22:58 UTCVendor advisory
- 2026-09-18 22:58 UTCGHSA enrichment
- 2026-09-18 19:28 UTCEPSS rescore
- 2026-09-18 10:40 UTCVendor advisory
- 2026-09-18 10:40 UTCGHSA enrichment
- 2026-09-17 22:14 UTCEG score recompute
- 2026-09-17 22:14 UTCVendor advisory
- 2026-09-17 22:14 UTCGHSA enrichment
- 2026-09-17 09:55 UTCVendor advisory
- 2026-09-17 09:55 UTCGHSA enrichment
- 2026-09-16 21:36 UTCEG score recompute
- 2026-09-16 21:36 UTCVendor advisory
- 2026-09-16 21:36 UTCGHSA enrichment
- 2026-09-16 14:08 UTCEPSS rescore
- 2026-09-16 09:16 UTCEG score recompute
- 2026-09-16 09:16 UTCVendor advisory
- 2026-09-16 09:16 UTCGHSA enrichment
- 2026-09-16 05:15 UTCEPSS rescore
- 2026-09-15 20:03 UTCVendor advisory
- 2026-09-15 20:02 UTCGHSA enrichment
- 2026-09-15 07:43 UTCEG score recompute
- 2026-09-15 07:43 UTCVendor advisory
- 2026-09-15 07:43 UTCGHSA enrichment
- 2026-09-15 03:12 UTCEPSS rescore
Show 75 moreShow fewer
- 2026-09-15 03:12 UTCEPSS rescore
- 2026-09-14 19:24 UTCVendor advisory
- 2026-09-14 19:24 UTCGHSA enrichment
- 2026-09-14 07:02 UTCVendor advisory
- 2026-09-14 07:02 UTCGHSA enrichment
- 2026-09-13 18:44 UTCEG score recompute
- 2026-09-13 18:44 UTCVendor advisory
- 2026-09-13 18:44 UTCGHSA enrichment
- 2026-09-13 06:25 UTCVendor advisory
- 2026-09-13 06:25 UTCGHSA enrichment
- 2026-09-12 18:07 UTCEG score recompute
- 2026-09-12 18:07 UTCVendor advisory
- 2026-09-12 18:07 UTCGHSA enrichment
- 2026-09-12 18:06 UTCGHSA enrichment
- 2026-09-12 05:47 UTCVendor advisory
- 2026-09-12 05:47 UTCGHSA enrichment
- 2026-09-11 17:29 UTCEG score recompute
- 2026-09-11 17:29 UTCVendor advisory
- 2026-09-11 17:29 UTCGHSA enrichment
- 2026-09-11 14:53 UTCEPSS rescore
- 2026-09-11 14:53 UTCEPSS rescore
- 2026-09-11 05:05 UTCVendor advisory
- 2026-09-11 05:05 UTCGHSA enrichment
- 2026-09-10 16:46 UTCEG score recompute
- 2026-09-10 16:46 UTCVendor advisory
- 2026-09-10 16:46 UTCGHSA enrichment
- 2026-09-10 04:28 UTCVendor advisory
- 2026-09-10 04:28 UTCGHSA enrichment
- 2026-09-09 16:10 UTCVendor advisory
- 2026-09-09 16:10 UTCGHSA enrichment
- 2026-09-09 13:01 UTCVendor advisory
- 2026-09-09 13:01 UTCGHSA enrichment
- 2026-09-09 00:41 UTCEG score recompute
- 2026-09-09 00:41 UTCVendor advisory
- 2026-09-09 00:41 UTCGHSA enrichment
- 2026-09-08 22:01 UTCEPSS rescore
- 2026-09-08 06:56 UTCVendor advisory
- 2026-09-08 06:56 UTCGHSA enrichment
- 2026-09-07 18:32 UTCEG score recompute
- 2026-09-07 18:32 UTCVendor advisory
- 2026-09-07 18:32 UTCGHSA enrichment
- 2026-09-07 06:14 UTCVendor advisory
- 2026-09-07 06:14 UTCGHSA enrichment
- 2026-09-06 17:54 UTCEG score recompute
- 2026-09-06 17:54 UTCVendor advisory
- 2026-09-06 17:54 UTCGHSA enrichment
- 2026-09-06 13:48 UTCEPSS rescore
- 2026-09-06 05:35 UTCVendor advisory
- 2026-09-06 05:35 UTCGHSA enrichment
- 2026-09-05 17:16 UTCEG score recompute
- 2026-09-05 17:16 UTCVendor advisory
- 2026-09-05 17:16 UTCGHSA enrichment
- 2026-09-05 15:31 UTCEPSS rescore
- 2026-09-05 04:57 UTCVendor advisory
- 2026-09-05 04:57 UTCGHSA enrichment
- 2026-09-04 16:39 UTCEG score recompute
- 2026-09-04 16:39 UTCVendor advisory
- 2026-09-04 16:38 UTCGHSA enrichment
- 2026-09-04 05:07 UTCEPSS rescore
- 2026-09-04 04:16 UTCVendor advisory
- 2026-09-04 04:16 UTCGHSA enrichment
- 2026-09-03 15:56 UTCVendor advisory
- 2026-09-03 15:56 UTCGHSA enrichment
- 2026-09-03 03:29 UTCVendor advisory
- 2026-09-03 03:29 UTCGHSA enrichment
- 2026-09-02 15:10 UTCEG score recompute
- 2026-09-02 15:10 UTCVendor advisory
- 2026-09-02 15:10 UTCGHSA enrichment
- 2026-09-02 14:12 UTCEPSS rescore
- 2026-09-02 02:50 UTCGHSA enrichment
- 2026-09-01 14:31 UTCEG score recompute
- 2026-09-01 14:30 UTCGHSA enrichment
- 2026-09-01 13:54 UTCEPSS rescore
- 2026-09-01 04:40 UTCEPSS rescore
- 2026-09-01 04:40 UTCEPSS rescore
Related CVEs(same vendor + same CWE)
Same vendor
10 shownredhat
- CVE-2001-0825EG 10.0HIGH
- CVE-2001-1009EG 10.0EPSS p93HIGH
- CVE-2001-0554EG 10.0EPSS p99HIGH
- CVE-2001-1162EG 10.0EPSS p96HIGH
- CVE-2001-0414EG 10.0EPSS p100HIGH
- CVE-2001-0191EG 10.0EPSS p92HIGH
- CVE-2001-0301EG 10.0EPSS p91HIGH
- CVE-2001-0197EG 10.0EPSS p96HIGH
- CVE-2001-0233EG 10.0EPSS p96HIGH
- CVE-2001-0010EG 10.0EPSS p98HIGH
Same CWE
10 shownCWE-770
Frequently asked(5)
What is CVE-2026-80212?
When was CVE-2026-80212 disclosed?
Is CVE-2026-80212 actively exploited?
What is the CVSS score of CVE-2026-80212?
How do I remediate CVE-2026-80212?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-80212
Is Your Infrastructure Affected by CVE-2026-80212?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.