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
This flaw affects NLnet Labs Unbound DNS resolvers during DNSSEC validation. A maliciously controlled signed DNS zone can make a vulnerable resolver crash and may allow remote code execution. The vendor states Unbound 1.25.1 fixes the issue. No source in the bundle establishes active exploitation.
Executive priority
Treat this as urgent for DNS infrastructure. A successful attack could disrupt name resolution and may compromise resolver systems. Patch affected Unbound deployments quickly, starting with production recursive resolvers and internet-reachable resolver paths.
Technical view
Unbound 1.19.1 through 1.25.0 can mishandle deep-copied validator response data when DS sub-queries suspend after NSEC3 computational budget exhaustion. A struct-assignment bug preserves a source pointer, then later dereferences it after the source region is freed, causing use-after-free and possible arbitrary code execution.
Likely exposure
Organizations running Unbound 1.19.1 through 1.25.0 as DNSSEC-validating resolvers are the relevant exposure group. Exposure is higher where resolvers process queries that can reach attacker-controlled signed zones. Downstream OS packages need vendor-specific status checks.
Exploitation context
The provided sources describe remote exploitation by controlling a malicious signed zone and causing a vulnerable Unbound resolver to query it. The CVE is not marked KEV, and the bundle provides no evidence of active exploitation or public weaponization.
Researcher notes
The key bug class is use-after-free from an incorrect pointer overwrite during deep copy. The trigger depends on DNSSEC validation state involving DS sub-query suspension after NSEC3 computational budget exhaustion. Evidence for arbitrary code execution is stated as possible, not proven exploited.
Mitigation direction
Upgrade NLnet Labs Unbound to 1.25.1 or a vendor-fixed build.
Apply applicable Red Hat errata for affected Red Hat deployments.
Inventory resolver hosts and prioritize DNSSEC-validating Unbound services.
Check NLnet Labs and OS vendor advisories for package-specific guidance.
Monitor resolver crash rates until remediation is complete.
Validation and detection
Identify Unbound installations and record exact package versions.
Compare versions against the affected 1.19.1 through 1.25.0 range.
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.