CVE-2026-35501
Fixed in a distro release EPSS <1%CVSS 3.7
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.
Products: NLnet Labs unbound
Distro releases
| Release | Package | Fixed in |
|---|---|---|
| Amazon Linux 2023 | python3-unbound | 1.17.1-1.amzn2023.0.17 |
| Amazon Linux 2023 | unbound | 1.17.1-1.amzn2023.0.17 |
| Amazon Linux 2023 | unbound-anchor | 1.17.1-1.amzn2023.0.17 |
| Amazon Linux 2023 | unbound-devel | 1.17.1-1.amzn2023.0.17 |
| Amazon Linux 2023 | unbound-libs | 1.17.1-1.amzn2023.0.17 |
| Amazon Linux 2023 | unbound-utils | 1.17.1-1.amzn2023.0.17 |
| Debian 12 | unbound | no fix |
| Debian 13 | unbound | 1.26.2-0+deb13u1 |
| Debian 14 | unbound | 1.26.2-1 |
| Ubuntu 22.04 LTS | unbound | no fix |
| Ubuntu 24.04 LTS | unbound | no fix |
| Ubuntu 26.04 LTS | unbound | no fix |
| Ubuntu 26.10 | unbound | no fix |
| Ubuntu Pro 14.04 LTS | unbound | no fix |
| Ubuntu Pro 16.04 LTS | unbound | no fix |
| Ubuntu Pro 18.04 LTS | unbound | no fix |
| Ubuntu Pro 20.04 LTS | unbound | no fix |
| openSUSE Tumbleweed | unbound | 1.26.2-1.1 |