CVE-2025-11411: Possible domain hijacking via promiscuous records in the authority section
NLnet Labs Unbound up to and including version 1.24.1 is vulnerable to possible domain hijack attacks. Promiscuous NS RRSets that complement positive DNS replies in the authority section can be used to trick resolvers to update their delegation information for the zone. Usually these RRSets are used to update the resolver's knowledge of the zone's name servers. A malicious actor can exploit the possible poisonous effect by injecting NS RRSets (and possibly their respective address records) in a reply. This could be done for example by trying to spoof a packet or fragmentation attacks. Unbound would then proceed to update the NS RRSet data it already has since the new data has enough trust for it, i.e., in-zone data for the delegation point. Unbound 1.24.1 includes a fix that scrubs unsolicited NS RRSets (and their respective address records) from replies mitigating the possible poison effect. Unbound 1.24.2 includes an additional fix that scrubs unsolicited NS RRSets (and their respective address records) from YXDOMAIN and non-referral nodata replies, further mitigating the possible poison effect.
Other sources
Possible domain hijacking via promiscuous records in the authority section
— Microsoft
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
NLnet Labs Unboundto a version that resolves this vulnerability.Fixed in 1.24.2
Event History
Frequently Asked Questions
What is the severity of CVE-2025-11411?
CVE-2025-11411 has been assigned a critical severity level due to its potential for allowing domain hijacking attacks.
How do I fix CVE-2025-11411?
To mitigate CVE-2025-11411, upgrade Unbound to version 1.24.1 or later.
What types of attacks can CVE-2025-11411 lead to?
CVE-2025-11411 can lead to domain hijack attacks by enabling attackers to manipulate resolver delegation information.
Which versions of Unbound are vulnerable to CVE-2025-11411?
Unbound versions up to and including 1.24.0 are vulnerable to CVE-2025-11411.
Is there a workaround available for CVE-2025-11411?
There are no publicly documented workarounds for CVE-2025-11411; upgrading to a patched version is recommended.