In NLnet Labs Unbound 1.7.0 up to and including 1.25.1, when an auth/rpz zone has a configured primary hostname that resolves to BOGUS A/AAAA, it is still considered as a possible XFR endpoint. A malicious actor that can spoof the hostname's A/AAAA record (no valid RRSIG required) becomes the zone's XFR primary and can replaces the entire zone/the resolver's entire response policy.
Fix
Patch, vendor advisory and mitigation references on NVD 1
- https://www.nlnetlabs.nl/downloads/unbound/CVE-2026-50248.txt Vendor Advisory
Every line above is quoted from NVD, CISA, Microsoft, the vendor's own advisory or DISA; nothing is generated.
Change history 1
- First seenCVSS 6.5 · nlnetlabsNVD modified 2026-10-24 13:10
Affected (CPE criteria) 1
cpe:2.3:a:nlnetlabs:unbound:*:*:*:*:*:*:*:*
References 1
- https://www.nlnetlabs.nl/downloads/unbound/CVE-2026-50248.txt Vendor Advisory