CVE-2026-80212

HIGHPre-NVD 7.57.5
EchelonGraph scoreHIGH confidence

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, ghsa, secondary
Trending — 4 sources updated this week
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.5Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.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 computed
Severity75% × 45%
Exploitation0% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
40%
KEV
Not listed

Published

August 27, 2026

Last Modified

August 27, 2026

Advisory Details (2)

Auto-updated Aug 27, 2026
No patch confirmed yet.
generic

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

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

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

https://github.com/ruby/resolv

Vendor Advisories for CVE-2026-80212(1)

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

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 14× in last 7d / 14× 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.

  1. 2026-08-30 01:22 UTCEPSS rescore
  2. 2026-08-30 00:35 UTCGHSA enrichment
  3. 2026-08-29 12:16 UTCGHSA enrichment
  4. 2026-08-28 23:56 UTCEG score recompute
  5. 2026-08-28 23:56 UTCGHSA enrichment
  6. 2026-08-28 21:42 UTCEPSS rescore
  7. 2026-08-28 08:48 UTCGHSA enrichment
  8. 2026-08-27 20:28 UTCEG score recompute
  9. 2026-08-27 20:28 UTCGHSA enrichment
  10. 2026-08-27 20:18 UTCEG score recompute
  11. 2026-08-27 20:18 UTCGHSA enrichment
  12. 2026-08-27 17:27 UTCEG score recompute
  13. 2026-08-27 16:49 UTCEG score recompute
  14. 2026-08-27 16:43 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-80212?
CVE-2026-80212 is a high vulnerability 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 CVE-2026-80212 disclosed?
CVE-2026-80212 was first published in the National Vulnerability Database on August 27, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-80212 actively exploited?
CVE-2026-80212 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 60.1% of all scored CVEs.
What is the CVSS score of CVE-2026-80212?
CVE-2026-80212 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-80212?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-80212, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

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.