Track vulnerabilities like this one. Sign up free to get alerted when software you use is affected.
7.8

Unbound 1.25.0 and earlier may cache false DNS entries

published 10 days ago
Summary

The Unbound DNS resolver (up to version 1.25.0) can be fooled into storing incorrect address information if an attacker sends a crafted response. This could cause users to be directed to the wrong sites. Update Unbound to version 1.25.1 or later, or apply the provided patch, to stop the false data from being cached.

What to do

The CVE record does not list a fixed version. Check the vendor's site or the advisory links below - a fix may already be released.

Affected software
Ecosystem VendorProductAffected versions
Docker Hardened Images:Alpine:3.23 docker hardened images unbound All versions
Original advisory text
NLnet Labs Unbound up to and including version 1.25.0 is vulnerable to poisoning via promiscuous records for the…
NLnet Labs Unbound up to and including version 1.25.0 is vulnerable to poisoning via promiscuous records for the authority section. Promiscuous RRSets that complement DNS replies in the authority section can be used to trick Unbound to cache such records. If an adversary is able to attach such records in a reply (i.e., spoofed packet, fragmentation attack) he would be able to poison Unbound's cache. A malicious actor can exploit the possible poisonous effect by injecting RRSets other than NS that are also accompanied by address records in a reply, for example MX. This could be achieved by trying to spoof a reply packet or fragmentation attacks. Unbound would then accept the relative address records in the additional section and cache them if the authority RRSet has enough trust at this point, i.e., in-zone data for the delegation point. Unbound 1.25.1 contains a patch with a fix that disregards address records from the additional section if they are not explicitly relevant only to authority NS records, mitigating the possible poison effect. This is a complement fix to CVE-2025-11411.
References
Fix within
Internet-facing 60 days
Internal At next upgrade
  • Not known to be exploited
  • Needs hands-on effort to exploit (estimated)
  • Gives an attacker partial control (estimated)
Severity
7.8 High
Timeline
Published11 Nov 2026
Updated16 Nov 2026
First seen16 Nov 2026
Sources
Track software like this
Free during beta