CVE-2026-33278: Possible arbitrary code execution during DNSSEC validation
NLnet Labs Unbound 1.19.1 up to and including version 1.25.0 has a vulnerability in the DNSSEC validator that enables denial of service and possible remote code execution as a result of deep copying a data structure and erroneously overwriting a destination pointer. An adversary can exploit the vulnerability by controlling a malicious signed zone and querying a vulnerable Unbound. When DS sub-queries need to suspend validation due to NSEC3 computational budget exhaustion (introduced in Unbound 1.19.1), Unbound deep-copies response messages to preserve them across memory region teardown. A struct-assignment bug overwrites the destination's pointer with the source's pointer. After the sub-query region is freed, the resumed validator dereferences this dangling pointer, triggering a crash or potentially enabling arbitrary code execution. Unbound 1.25.1 contains a patch with a fix to preserve the correct pointer when deep copying the data structure.
Security readout for executives and security teams
Plain-English summary
A remote attacker who controls a signed DNS zone may crash a vulnerable Unbound resolver and could potentially execute code. No authentication or user interaction is required. The confirmed affected range is Unbound 1.19.1 through 1.25.0; version 1.25.1 fixes the defect.
Executive priority
Treat this as an emergency remediation for affected resolvers because compromise could disrupt DNS services or potentially enable code execution. Patch internet-accessible and high-dependency resolvers first. The absence of confirmed active exploitation reduces certainty about immediate attacks, but not the severity of successful exploitation.
Technical view
During DNSSEC validation, suspended DS sub-queries can trigger an incorrect deep copy after NSEC3 budget exhaustion. A struct assignment replaces the destination pointer with a source-region pointer. When that region is freed, resumed validation dereferences a dangling pointer, causing a use-after-free, resolver crash, or possible arbitrary code execution.
Likely exposure
Organizations running Unbound 1.19.1 through 1.25.0 are potentially exposed when untrusted parties can cause the resolver to query attacker-controlled signed zones. Exposure includes directly reachable resolvers and restricted resolvers accepting queries from potentially compromised clients. The supplied evidence does not quantify deployment prevalence.
Exploitation context
The attack is remote, unauthenticated, and requires control of a malicious signed DNS zone plus a query reaching the vulnerable resolver. The source bundle reports possible code execution and reliable denial-of-service impact. CISA KEV status is false, and no supplied source establishes active exploitation; exploit maturity is recorded as unknown.
Researcher notes
This is a DNSSEC validator use-after-free corresponding to CWE-416 and CWE-672. The vulnerable path was introduced with NSEC3 computational-budget handling in 1.19.1. The patch preserves the correct destination pointer during deep copying. The supplied evidence establishes potential, not demonstrated, arbitrary code execution; researchers should avoid equating a crash with confirmed code execution.
Mitigation direction
Upgrade Unbound to 1.25.1 or a vendor-provided package containing the fix.
Review applicable operating-system vendor advisories and install their corrected packages.
Until patched, limit untrusted query access to affected resolvers where operationally feasible.
Prioritize externally reachable and business-critical recursive resolvers.
Validation and detection
Inventory Unbound versions across appliances, servers, containers, and embedded deployments.
Confirm no deployed instance remains between versions 1.19.1 and 1.25.0 inclusive.
Verify distribution packages against applicable vendor errata, not upstream version strings alone.
Review resolver crash and restart records, while recognizing absence of crashes does not prove safety.
Confirm resolver health and DNSSEC validation behavior after remediation.
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-416: 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.
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program 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.
2CVSS vectors
9Timeline events
2ADP providers
8Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: yesTechnical Impact: total
CVSS vector scores
2 official scores
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-416 · source CWE mapping
Use After Free
Use After Free represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Operation on a Resource after Expiration or Release
Operation on a Resource after Expiration or Release represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.