CVE-2026-80212Patch

LOWCVSS 7.5 · HIGH

Signal is active with 1 mentions in latest observed window

Immediate actions

  • Patch affected systems immediately

Recommended action window: Monitor and triage in normal cycle

NVD description

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.

0.5/ 10 priority

Sources & remediation

Weakness type (CWE)
CWE-770

Priority

LOW

Exploitation

NONE

PoC

NONE

Patch

AVAILABLE

Momentum

STABLE

Threat summary

  • Patch or workaround signal is available
  • 3 mentions across 2 observed days
  • Momentum state: stable

What's happening

  • Patch or workaround mentioned in 2 signals
  • Technical details provided in 2 signals
  • Disclosure: 1 classified signal
  • Peaked 1d ago at 2 mentions (2026-08-27); latest day: 1
  • 3 total mentions across 2 days

Deep dive

Activity timeline3 mentions / 2d
01122Mentions · 2026-08-27: 2Mentions · 2026-09-25: 1Patch / Workaround · 2026-08-27: 2Technical Details · 2026-08-27: 1Technical Details · 2026-09-25: 108-2709-25
Signal classification2 categories
Patch
266.7%
Disclosure
133.3%
Referenced assets1 URL
Classification over time
DateTotalLabels
2026-08-272
Patch2
2026-09-251
Disclosure1
Full discourse3 posts
  • Hiroshi SHIBATA@hsbt
    Patch

    resolv 0.7.2 and 0.3.2 are out, fixing CVE-2026-80212 (memory exhaustion) and CVE-2026-80213 (hostname validation bypass). Only code that resolves names through the resolv gem is affected. Ordinary socket and Net::HTTP connections are not. https://www.ruby-lang.org/en/news/2026/08/27/multiple-vulnerabilities-in-resolv/

    Post summary

    Ruby’s resolv gem released updates for CVE‑2026‑80212 and CVE‑2026‑80213, addressing memory exhaustion and hostname validation bypass; only gem‑based name resolution is affected.

    0802722.2K
    7.8K followersView on X
  • Fujihashi Yuya|Webエンジニア@FujihashiYuya
    Disclosure

    CVE-2026-80212 はメモリ枯渇。 攻撃者が影響を与えられるホスト名を解決すると、悪意あるDNS応答でプロセスがメモリを際限なく消費させられる。 ユーザーがURLを入力できる機能があると、そこが入口になりうる。

    Post summary

    The text discloses CVE‑2026‑80212 as a memory‑exhaustion vulnerability that can be exploited by a malicious DNS response when resolving a compromised hostname, potentially accessible through user‑controlled URL input.

    1001049
    25 followersView on X
  • Sergio Pereda@chapuzon
    Patch

    🔒 Nuevas amenazas encontradas en el gem 'resolv' de Ruby: CVE-2026-80212 y CVE-2026-80213. ¡Asegura tus aplicaciones actualizando a la versión 0.7.2! Infórmate aquí: https://www.ruby-lang.org/en/news/2026/08/27/multiple-vulnerabilities-in-resolv/ #Ciberseguridad

    Post summary

    The message announces CVE-2026-80212 and CVE-2026-80213 in Ruby's resolv gem and recommends updating to version 0.7.2 for mitigation.

    0000075
    121 followersView on X

Explore more