CVE-2026-42960
DNS Cache Poisoning in Unbound DNS Server
Publication date: 2026-05-20
Last updated on: 2026-05-20
Assigner: NLnet Labs
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| nlnet_labs | unbound | to 1.25.0 (inc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-349 | The product, when processing trusted data, accepts any untrusted data that is also included with the trusted data, treating the untrusted data as if it were trusted. |
Attack-Flow Graph
AI Powered Q&A
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
The provided information does not specify how CVE-2026-42960 affects compliance with common standards and regulations such as GDPR or HIPAA.
How can this vulnerability impact me? :
This vulnerability can impact you by allowing attackers to poison the DNS cache of your Unbound DNS resolver.
Cache poisoning can cause your DNS resolver to return incorrect DNS information, potentially redirecting users to malicious websites, intercepting or manipulating network traffic, or causing denial of service by disrupting DNS resolution.
Such impacts can compromise security, privacy, and the integrity of your network communications.
What immediate steps should I take to mitigate this vulnerability?
To mitigate the vulnerability CVE-2026-42960 in Unbound DNS software, the immediate step is to upgrade Unbound to version 1.25.1 or later, where the issue is fixed.
Alternatively, users running version 1.25.0 can apply a manual patch available from the Unbound website and then recompile the software to address the vulnerability.
Can you explain this vulnerability to me?
CVE-2026-42960 is a vulnerability in the Unbound DNS software up to version 1.25.0 that allows an attacker to poison the DNS cache by exploiting promiscuous resource record sets (RRSets) in DNS replies.
An attacker can send spoofed or fragmented DNS reply packets containing address records such as MX records alongside authority NS records. If the authority RRSet is trusted by Unbound, it may cache these malicious address records, leading to cache poisoning.
This means Unbound can be tricked into storing and serving incorrect DNS information, which can redirect users to malicious sites or disrupt DNS resolution.
The vulnerability was fixed in Unbound version 1.25.1 by ignoring address records in the additional section unless they are explicitly relevant to authority NS records.