CVE-2026-35501

Bypass of a configured island trust anchor underneath an insecure parent from an atacker-controlled NSEC record.

  • Low 3.7

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.

Key facts

Published
21 Oct 2026
Last changed
29 Oct 2026
Assigned by
NLnet Labs
EPSS
0.111% likely to be exploited in the next 30 days, higher than 1.356% of CVEs (scores for 17 Nov 2026)
SSVC (CISA)
Exploitation: none; Automatable: no; Technical impact: partial

Severity scores

Each score is shown as its source gave it. They are not averaged or merged.

  • 3.7CVSS 3.1, Lowfrom the CNA (NLnet Labs)CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N

What to do

  • This issue is fixed starting with version 1.26.2CNA solution statement

Historical context and remediation

This reference retains the original CVE publication date. A recent record update does not mean a new attack occurred.

No separately sourced impact summary is available on this page yet. Consult the description, version data and dated exploitation evidence.

Version statuses below come from the CNA. An “unaffected” version is not necessarily a currently supported release or proof of a patch date. EPSS is a dated risk estimate, not a count of historical attacks.

Read the original CVE record.

Affected products

VendorProductVersions
NLnet LabsUnbound
  • Default status: unaffected
  • 1.0.1 up to but excluding 1.26.2 (affected)

Timeline

  1. 13 May 2026 Issue reported by Qifan Zhang
  2. 8 Jun 2026 NLnet Labs shares patch
  3. 13 Jun 2026 Qifan Zhang verifies patch
  4. 21 Oct 2026 Fixes released with version 1.26.2
  5. 21 Oct 2026 Published

Weakness

References