3.7
Low
CVE-2026-35501 When NLnet Labs Unbound 1.0.1 up to and including version 1.26.1 is configured with both a root trust anchor and an…
Description
When NLnet Labs Unbound 1.0.1 up to and including version 1.26.1 is configured with both a root trust anchor and an additional 'trust-anchor:' for an island-of-security zone whose parent is provably insecure under the root chain, a malicious actor with a forged NSEC reply with the SOA bit cleared can trick Unbound to treat the configured trust island as insecure. This happens because the DNSSEC validator in Unbound accepts and caches the NSEC insecure response bypassing the RRSIG validation that the validator was supposed to do. The acceptance of the NSEC record at the trust anchor apex was allowed due to and old fix for type DS and NSEC queries from clients when trust anchor for that name existed.
Affected products and versions
| Product | Affected versions | Fixed in |
|---|---|---|
| unbound 1.0 | 1.0.1 → < 1.26.2 | 1.26.2 |
References
- www.nlnetlabs.nl www.nlnetlabs.nl
Timeline
- Published
- Last modified
Other CVEs of unbound
The 58 CVEs of unbound →
CVE-2026-97206
NLnet Labs Unbound, 1.22.0 up to and including version 1.26.1, contains a DNS-over-QUIC (DoQ) lifetime bug reachable…
7.5
High
CVE-2026-96405
NLnet Labs Unbound up to and including version 1.26.1 limits compression-pointer traversal for each individual…
5.3
Medium
CVE-2026-50106
When NLnet Labs Unbound up to and including version 1.26.1 is configured with both a root trust anchor and an additional…
6.5
Medium
CVE-2026-109125
In NLnet Labs Unbound up to and including version 1.26.1, an observable cache-level side-channel can be exposed with…
5.3
Medium