CVE-2026-80212

HIGHPre-NVD 7.57.5
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

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.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Trending — 4 sources updated this week
7.5EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 7.5Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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.

CVSS v3
7.5
EG Score
7.5HIGHmedium confidence
EG Risk
49
EG Risk 49/100

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 computed (value × EchelonGraph’s weight)
Severity75% × 45%
The EG Score, 7.5 of 10.
Exploitation0.4% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.4%
EPSS %ILE
32nd
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; 60 days if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

August 27, 2026

Last Modified

September 9, 2026

Advisory Details (2)

Auto-updated Aug 27, 2026
Patch available.
Web page

Security advisories: CVE-2026-80212 and CVE-2026-80213 | Ruby

https://www.ruby-lang.org/en/news/2026/08/27/multiple-vulnerabilities-in-resolv/
Web page

GitHub - ruby/resolv: A thread-aware DNS resolver library written in Ruby · GitHub

https://github.com/ruby/resolv

Vendor Advisories for CVE-2026-80212(13)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(12)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatruby-0:3.3.12-15.el10_22026-10-02redhat
redhatruby:2.5-8100020260923114349.489197e62026-09-30redhat
redhatruby4.0-0:4.0.6-37.el10_22026-09-28redhat
redhatruby:4.0-9080020260909091105.92026-09-28redhat
redhatruby:3.3-9080020260909091103.92026-09-28redhat
redhatruby-0:3.0.7-168.el9_82026-09-28redhat
redhatruby:3.3-8100020260909091101.489197e62026-09-28redhat
redhatruby3-3-main-3.3.10-23.6.hum12026-09-02redhat
redhatruby4-0-main-4.0.6-37.3.hum12026-09-02redhat
redhatruby3-4-main-3.4.10-31.6.hum12026-08-21redhat
redhatruby3-3-main-3.3.10-23.5.hum12026-08-21redhat
redhatruby4-0-main-4.0.6-37.2.hum12026-08-20redhat

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 27× in last 7d / 153× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 100 of 247 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 147 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-13 16:35 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  2. 2026-10-13 06:32 UTCEG score recompute
  3. 2026-10-13 06:32 UTCVendor advisory
  4. 2026-10-13 06:31 UTCGHSA enrichmentGHSA-x2vh-ff4w-v64c · GitHub severity HIGH · GitHub CVSS 7.5
  5. 2026-10-12 16:35 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  6. 2026-10-12 14:57 UTCEG score recompute
  7. 2026-10-11 19:21 UTCEG score recompute
  8. 2026-10-11 16:37 UTCEG score recompute
  9. 2026-10-11 13:56 UTCEG score recompute
  10. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  11. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  12. 2026-10-10 14:21 UTCVendor advisory
  13. 2026-10-10 14:21 UTCGHSA enrichmentGHSA-x2vh-ff4w-v64c · GitHub severity HIGH · GitHub CVSS 7.5
  14. 2026-10-10 01:56 UTCEG score recompute
  15. 2026-10-10 01:56 UTCVendor advisory
  16. 2026-10-10 01:56 UTCGHSA enrichmentGHSA-x2vh-ff4w-v64c · GitHub severity HIGH · GitHub CVSS 7.5
  17. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  18. 2026-10-09 03:08 UTCEG score recompute
  19. 2026-10-09 03:08 UTCVendor advisory
  20. 2026-10-09 03:08 UTCGHSA enrichmentGHSA-x2vh-ff4w-v64c · GitHub severity HIGH · GitHub CVSS 7.5
  21. 2026-10-08 17:13 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  22. 2026-10-08 01:21 UTCEG score recompute
  23. 2026-10-08 01:21 UTCVendor advisory
  24. 2026-10-08 01:21 UTCGHSA enrichmentGHSA-x2vh-ff4w-v64c · GitHub severity HIGH · GitHub CVSS 7.5
  25. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
Show 75 more
  1. 2026-10-07 09:06 UTCVendor advisory
  2. 2026-10-07 09:06 UTCGHSA enrichmentGHSA-x2vh-ff4w-v64c · GitHub severity HIGH · GitHub CVSS 7.5
  3. 2026-10-06 20:42 UTCEG score recompute
  4. 2026-10-06 20:42 UTCVendor advisory
  5. 2026-10-06 20:41 UTCGHSA enrichmentGHSA-x2vh-ff4w-v64c · GitHub severity HIGH · GitHub CVSS 7.5
  6. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  7. 2026-10-06 07:33 UTCEG score recompute
  8. 2026-10-06 07:33 UTCVendor advisory
  9. 2026-10-06 07:33 UTCGHSA enrichmentGHSA-x2vh-ff4w-v64c · GitHub severity HIGH · GitHub CVSS 7.5
  10. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  11. 2026-10-05 16:54 UTCVendor advisory
  12. 2026-10-05 16:54 UTCGHSA enrichmentGHSA-x2vh-ff4w-v64c · GitHub severity HIGH · GitHub CVSS 7.5
  13. 2026-10-05 04:36 UTCEG score recompute
  14. 2026-10-05 04:36 UTCVendor advisory
  15. 2026-10-05 04:36 UTCGHSA enrichmentGHSA-x2vh-ff4w-v64c · GitHub severity HIGH · GitHub CVSS 7.5
  16. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  17. 2026-10-04 15:58 UTCVendor advisory
  18. 2026-10-04 15:58 UTCGHSA enrichmentGHSA-x2vh-ff4w-v64c · GitHub severity HIGH · GitHub CVSS 7.5
  19. 2026-10-04 03:32 UTCVendor advisory
  20. 2026-10-04 03:32 UTCGHSA enrichmentGHSA-x2vh-ff4w-v64c · GitHub severity HIGH · GitHub CVSS 7.5
  21. 2026-10-03 15:14 UTCEG score recompute
  22. 2026-10-03 15:14 UTCVendor advisory
  23. 2026-10-03 15:14 UTCGHSA enrichmentGHSA-x2vh-ff4w-v64c · GitHub severity HIGH · GitHub CVSS 7.5
  24. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  25. 2026-10-02 21:31 UTCEG score recompute
  26. 2026-10-02 21:31 UTCVendor advisory
  27. 2026-10-02 21:31 UTCGHSA enrichmentGHSA-x2vh-ff4w-v64c · GitHub severity HIGH · GitHub CVSS 7.5
  28. 2026-10-02 17:57 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  29. 2026-10-02 09:08 UTCVendor advisory
  30. 2026-10-02 09:08 UTCGHSA enrichmentGHSA-x2vh-ff4w-v64c · GitHub severity HIGH · GitHub CVSS 7.5
  31. 2026-10-01 20:45 UTCEG score recompute
  32. 2026-10-01 20:45 UTCVendor advisory
  33. 2026-10-01 20:45 UTCGHSA enrichmentGHSA-x2vh-ff4w-v64c · GitHub severity HIGH · GitHub CVSS 7.5
  34. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  35. 2026-10-01 08:13 UTCVendor advisory
  36. 2026-10-01 08:13 UTCGHSA enrichmentGHSA-x2vh-ff4w-v64c · GitHub severity HIGH · GitHub CVSS 7.5
  37. 2026-09-30 19:55 UTCEG score recompute
  38. 2026-09-30 19:55 UTCVendor advisory
  39. 2026-09-30 19:55 UTCGHSA enrichmentGHSA-x2vh-ff4w-v64c · GitHub severity HIGH · GitHub CVSS 7.5
  40. 2026-09-30 15:04 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  41. 2026-09-30 05:04 UTCEG score recompute
  42. 2026-09-30 05:04 UTCVendor advisory
  43. 2026-09-30 05:04 UTCGHSA enrichmentGHSA-x2vh-ff4w-v64c · GitHub severity HIGH · GitHub CVSS 7.5
  44. 2026-09-29 12:17 UTCEG score recompute
  45. 2026-09-29 12:17 UTCVendor advisory
  46. 2026-09-29 12:17 UTCGHSA enrichmentGHSA-x2vh-ff4w-v64c · GitHub severity HIGH · GitHub CVSS 7.5
  47. 2026-09-28 21:17 UTCEG score recompute
  48. 2026-09-28 21:17 UTCVendor advisory
  49. 2026-09-28 21:17 UTCGHSA enrichmentGHSA-x2vh-ff4w-v64c · GitHub severity HIGH · GitHub CVSS 7.5
  50. 2026-09-28 13:52 UTCEPSS rescoreEPSS 0.6% · 44th percentile
  51. 2026-09-28 07:47 UTCVendor advisory
  52. 2026-09-28 07:47 UTCGHSA enrichmentGHSA-x2vh-ff4w-v64c · GitHub severity HIGH · GitHub CVSS 7.5
  53. 2026-09-27 19:29 UTCEG score recompute
  54. 2026-09-27 19:29 UTCVendor advisory
  55. 2026-09-27 19:29 UTCGHSA enrichmentGHSA-x2vh-ff4w-v64c · GitHub severity HIGH · GitHub CVSS 7.5
  56. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.6% · 44th percentile
  57. 2026-09-27 07:05 UTCVendor advisory
  58. 2026-09-27 07:05 UTCGHSA enrichmentGHSA-x2vh-ff4w-v64c · GitHub severity HIGH · GitHub CVSS 7.5
  59. 2026-09-26 18:46 UTCEG score recompute
  60. 2026-09-26 18:46 UTCVendor advisory
  61. 2026-09-26 18:46 UTCGHSA enrichmentGHSA-x2vh-ff4w-v64c · GitHub severity HIGH · GitHub CVSS 7.5
  62. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.6% · 44th percentile
  63. 2026-09-26 00:28 UTCEPSS rescoreEPSS 0.6% · 44th percentile
  64. 2026-09-25 15:46 UTCVendor advisory
  65. 2026-09-25 15:46 UTCGHSA enrichmentGHSA-x2vh-ff4w-v64c · GitHub severity HIGH · GitHub CVSS 7.5
  66. 2026-09-25 02:51 UTCVendor advisory
  67. 2026-09-25 02:51 UTCGHSA enrichmentGHSA-x2vh-ff4w-v64c · GitHub severity HIGH · GitHub CVSS 7.5
  68. 2026-09-24 14:32 UTCEG score recompute
  69. 2026-09-24 14:32 UTCVendor advisory
  70. 2026-09-24 14:32 UTCGHSA enrichmentGHSA-x2vh-ff4w-v64c · GitHub severity HIGH · GitHub CVSS 7.5
  71. 2026-09-24 14:04 UTCEPSS rescoreEPSS 0.6% · 44th percentile
  72. 2026-09-24 02:07 UTCEG score recompute
  73. 2026-09-24 02:07 UTCVendor advisory
  74. 2026-09-24 02:07 UTCGHSA enrichmentGHSA-x2vh-ff4w-v64c · GitHub severity HIGH · GitHub CVSS 7.5
  75. 2026-09-23 17:54 UTCEPSS rescoreEPSS 0.6% · 45th percentile

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-80212?
CVE-2026-80212 is a high-severity vulnerability; its CVE record was published on August 27, 2026. 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…
When was the CVE record for CVE-2026-80212 published?
The CVE record for CVE-2026-80212 was published on August 27, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of September 9, 2026; the record at its source may have been updated since.
Is CVE-2026-80212 actively exploited?
CVE-2026-80212 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (32nd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-80212?
CVE-2026-80212 has a CVSS base score of 7.5 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-80212?
A fix for CVE-2026-80212 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-80212 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-80212

Explore →

Is Your Infrastructure Affected by CVE-2026-80212?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs