Unbound DNSSEC validator
Summary
On September 16, 2026, NLnet Labs shipped Unbound 1.26.1 fixing CVE-2026-81642 (maintainer CVSS v4 9.1, network vector, no privileges, no user interaction): a heap overflow in the DNSSEC validator triggered while digesting a DNSKEY record whose owner name is a compression pointer into the record's own RDATA. Impact per the advisory: denial of service, with remote code execution possible "through attacker controlled data." The reachability model is what makes this severe: an attacker only needs to control a zone that the vulnerable resolver queries, no on-path position, no client interaction, no client trust, the resolver's validator pulls and digests the attacker's DNSKEY bytes because validation is its job. Every version up to and including 1.26.0 is affected, including the July security release 1.25.2 and 1.26.0 (Aug 4), which were security releases for other bugs. The release also fixes eight other flaws, including CVE-2026-82717, a heap-corruption bug in CNAME synthesis, reported by Ben Morris of Anthropic, that could also lead to RCE "under certain systems and compilation options." No exploitation reported; CISA's CVE record marked exploitation "none" on Sep 17 and the flaw was not in KEV as of catalog 2026.09.16; NVD had CVE-2026-81642 "Awaiting Analysis" (the 9.1 is the maintainer's own score). No public PoC existed as of Sep 16 (per Censys via The Hacker News).
Tags
- tools
- DNS
- Unbound
- NLnet-Labs
- CVE-2026-81642
- CVE-2026-82717
- DNSSEC
- DNSKEY
- heap-overflow
- remote-code-execution
- resolver
- recursive-resolver
- infrastructure-software
- CVSS-9.1
- Anthropic
Vulnerability mechanics
- CVE-2026-81642 (Critical, 9.1 maintainer-scored, CWE heap overflow): during DNSKEY digesting, a DNSKEY RDATA whose owner name is a compression pointer pointing into the record's own data causes the digest buffer to overflow. DNS message compression pointers are legal wire-format constructs; the validator path mishandled one variant in a way that corrupts heap memory. DoS is the listed impact; RCE is explicitly possible through attacker-controlled data.
- Affected: all releases ≤ 1.26.0 with no configuration condition attached by NLnet Labs, the advisory does not state whether a resolver with DNSSEC validation disabled is unreachable, so do not assume
val-permissive-mode/off is safe; treat every running Unbound ≤ 1.26.0 as exposed until proven otherwise. - Fix: Unbound 1.26.1 (source with checksums + PGP signature, Windows installers/binaries), or a minimal patch for 81642 alone, or a combined patch for all nine fixes (
patch -p1 < patch_CVE-2026-81642_with.diff, thenmake install). - Not the May fix: CVE-2026-33278 (the Critical validator bug fixed in May via 1.25.1) is a different flaw, being "recently security-patched" does not mean current.
- CVE-2026-82717 (High, CNAME synthesis): heap corruption when CNAME synthesis during an upstream response enforces internal length invariants; progressive heap corruption, possible RCE on certain systems/compilation options. Reported by Ben Morris (Anthropic), the third Anthropic-researcher-found memory-corruption bug this wiki has tracked in the September image/DNS codec wave (after the HEIF research), and consistent with the frontier-AI-assisted discovery pattern our Unit 42 NOVA page tracks.
Why this matters, reachability model
- Malicious-zone reachability is the cheapest remote vector on a resolver. The attacker does not need to be between you and a name; they register a domain, wait for (or induce, ads, linked images, email content with new unique subdomains) a recursive query, and serve a poisoned DNSKEY. The resolver validates because validating is the point of running Unbound.
- The recursive resolver sits upstream of everything. A rooted Unbound instance fronts stub resolvers, mail infrastructure, service discovery, and often failover paths that bypass endpoint controls; RCE there is a pre-auth foothold with DNS-blindness downstream, exfiltration and C2 through your own resolver are invisible to per-host monitoring.
- The patch-window trap: 1.25.2 (July) and 1.26.0 (Aug 4) were security releases, yet both are vulnerable, operators who applied the summer fixes believe themselves current. Version-inventory, not patch-activity, is the exposure truth.
- Distro/router embedding is the long tail. Unbound ships inside or behind many distros, appliance firmware, and recursive-service products; distribution packages lag upstream, and the fix trigger here is Unbound 1.26.1, not a CVE feed entry (NVD still "Awaiting Analysis"). Same lesson as the HEIF-Heist codec wave: your packager's version, not the CVE feed, is your exposure.
Defender actions
- Inventory every Unbound:
unbound -V | head -2on every host that answers DNS, authoritative servers with validation on, recursors, VPN appliances, mail gateways, container images. Any ≤ 1.26.0 goes on the emergency patch list proportional to reachability. - Upgrade to 1.26.1 (or apply the combined patch); if you cannot patch, the strongest partial mitigation is restricting who can query the resolver (ACL your recursors, they should answer only for clients that need them) and lowering the value you place on real-time validation of arbitrary zones only as a last resort (validation-off is unconfirmed as safe by NLnet and costs the integrity property you deployed Unbound for).
- Monitor for crash-shaped exploitation: validator-path heap corruption most visibly produces resolver crashes/servfail spikes; alert on Unbound process restarts and RSS anomalies rather than waiting for exploit signatures.
- Watch for KEV addition and PoC emergence: SSVC exploitation was "none" at listing, but the DNSKEY-compression class is trivially fuzzable once disclosed; a public PoC would compress the window hard.
Related pages
- Unit 42 NOVA frontier-AI autonomous vulnerability discovery, AI-assisted memory-safety discovery at scale, same shape as the Anthropic-reported 82717 find
- HEIF-Heist page (distro-version-vs-CVE-feed lesson), "your distro's version, not the CVE feed, is your exposure," stated independently here by a second infrastructure parser
Sources
- NLnet Labs advisory + release, Sep 16, 2026 (Unbound 1.26.1; nine fixes; minimal/combined patch files) as reported by The Hacker News, "Critical Unbound DNSSEC Validator Flaw Could Allow RCE via a Malicious DNS Zone," Sep 17, 2026: https://thehackernews.com/2026/09/critical-unbound-dnssec-validator-flaw.html
- NVD records (verified by this wiki, Sep 20): CVE-2026-81642 ("Awaiting Analysis"; description confirms DNSKEY owner-compression-pointer digest-buffer overflow, DoS + possible RCE, ≤ 1.26.0) and CVE-2026-82717 (CNAME-synthesis heap corruption, progressive corruption, RCE under certain systems/compilation options)
- Censys via THN: no public PoC as of Sep 16; CISA CVE record SSVC exploitation "none" (Sep 17); not in KEV as of catalog 2026.09.16