Improperly Controlled Sequential Memory Allocation Affecting resolv package, versions <0.3.2>=0.4.0, <0.7.2
Threat Intelligence
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applications- Snyk IDSNYK-RUBY-RESOLV-19477214
- published1 Sept 2026
- disclosed29 Aug 2026
- creditUnknown
Introduced: 29 Aug 2026
NewCVE-2026-80212 (opens in a new tab)How to fix?
Upgrade resolv to version 0.3.2, 0.7.2 or higher.
Overview
resolv is a Thread-aware DNS resolver library in Ruby.
Affected versions of this package are vulnerable to Improperly Controlled Sequential Memory Allocation due to permanent class registration in Resolv::DNS::Resource::Generic.create, Resolv::DNS::SvcParam::Generic.create, and the related DNS resource class lookup in lib/resolv.rb. An attacker can grow process memory without bound by sending DNS responses that contain large numbers of unknown (type, class) pairs or unknown SvcParamKey values. Each decoded unknown value creates a new class that is kept alive in a constant and ClassHash after the response is discarded, so repeated malicious responses accumulate unreclaimed memory and can exhaust the Ruby process.