CVE-2026-42944: Heap overflow with multiple NSID, COOKIE, PADDING EDNS options
NLnet Labs Unbound 1.14.0 up to and including version 1.25.0 has a vulnerability that results in heap overflow when encoding multiple NSID and/or DNS Cookie EDNS and/or EDNS Padding options in the reply packet. The relevant options ('nsid', 'answer-cookie', 'pad-responses' (default)) need to be enabled for the vulnerability to be exploited. An adversary who can query Unbound can exploit the vulnerability by attaching multiple NSID and/or DNS Cookie EDNS and/or EDNS Padding options to the query. A flaw in the size calculation of the EDNS field truncates the correct value which allows the encoder to overflow the available space when writing. Those two combined lead to a heap overflow write of Unbound controlled data and eventually a crash. Unbound 1.25.1 contains a patch with a fix to de-duplicate the EDNS options and a fix to prevent truncation of the EDNS field size calculation.
Security readout for executives and security teams
Plain-English summary
A remote, unauthenticated client that can query a vulnerable Unbound DNS resolver may trigger a heap overflow and crash the service. This can disrupt DNS resolution and dependent business services. Exploitation requires affected EDNS response options to be enabled; response padding is enabled by default.
Executive priority
Prioritize rapid remediation for externally reachable or business-critical resolvers because successful exploitation can interrupt DNS-dependent services without authentication. Patch other reachable affected instances promptly after exposure validation. There is no cited evidence of active exploitation, so urgency should reflect service criticality and accessibility rather than assumed compromise.
Technical view
Unbound 1.14.0 through 1.25.0 incorrectly calculates the EDNS field size when multiple NSID, DNS Cookie, or Padding options are supplied. Truncation during size calculation lets the encoder write beyond allocated heap space. The documented outcome is a crash and high availability impact. Version 1.25.1 de-duplicates options and prevents size truncation.
Likely exposure
Exposure includes vulnerable Unbound resolvers that accept queries from untrusted or compromised clients and have relevant options enabled: nsid, answer-cookie, or pad-responses. Internet-accessible resolvers are the clearest concern, but internal resolvers may also be reachable from compromised endpoints. Configuration and network reachability determine actual exposure.
Exploitation context
Attack complexity is rated low, with no privileges or user interaction required. However, the supplied record is not in KEV and provides no evidence of active exploitation. The documented security consequence is denial of service through a process crash, not code execution.
Researcher notes
The root causes map to incorrect allocation sizing, integer truncation, and out-of-bounds heap writing. The vendor describes Unbound-controlled overflow data and an eventual crash. The supplied evidence does not establish practical code execution, so assessments should avoid upgrading the impact beyond availability loss without additional validated research.
Mitigation direction
Upgrade affected Unbound installations to version 1.25.1 or a vendor-packaged fixed release.
Apply the applicable operating-system vendor security update where Unbound is distribution-managed.
Until patched, restrict resolver access to trusted networks and clients.
Consider disabling relevant EDNS response options where operationally acceptable, then monitor for DNS compatibility issues.
Validation and detection
Inventory Unbound versions across authoritative, recursive, embedded, and appliance deployments.
Review configurations for nsid, answer-cookie, and pad-responses settings.
Confirm whether untrusted or compromised clients can query each resolver.
Verify upgraded instances report version 1.25.1 or a vendor-confirmed fixed package.
Review service logs and monitoring for unexplained Unbound crashes or restarts.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-131: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-131 · source CWE mapping
Incorrect Calculation of Buffer Size
Incorrect Calculation of Buffer Size represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Numeric Truncation Error represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Out-of-bounds Write represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.