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 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.
Configurations

No configuration.

History

21 Oct 2026, 09:17

Type Values Removed Values Added
New CVE

Information

Published : 2026-10-21 09:17

Updated : 2026-10-29 19:17


NVD link : CVE-2026-35501

Mitre link : CVE-2026-35501

CVE.ORG link : CVE-2026-35501


JSON object : View

Products Affected

No product.

CWE
CWE-354

Improper Validation of Integrity Check Value