CVE-2026-33278
Denial of Service and Code Execution in Unbound DNSSEC Validator
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) |
| nlnet_labs | unbound | 1.25.1 |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-416 | The product reuses or references memory after it has been freed. At some point afterward, the memory may be allocated again and saved in another pointer, while the original pointer references a location somewhere within the new allocation. Any operations using the original pointer are no longer valid because the memory "belongs" to the code that operates on the new pointer. |
| CWE-672 | The product uses, accesses, or otherwise operates on a resource after that resource has been expired, released, or revoked. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
CVE-2026-33278 is a vulnerability in the DNSSEC validator component of NLnet Labs Unbound versions 1.19.1 through 1.25.0. It occurs due to a bug in deep copying a data structure where a destination pointer is mistakenly overwritten with a source pointer. This happens when Unbound suspends validation because of NSEC3 computational budget exhaustion. The incorrect pointer leads to a dangling pointer that, when dereferenced, can cause the validator to crash or potentially allow an attacker to execute arbitrary code remotely.
How can this vulnerability impact me? :
This vulnerability can impact you by causing a denial of service (DoS) condition where the DNSSEC validator crashes, disrupting DNS resolution services. More severely, it may allow an attacker who controls a malicious signed DNS zone to execute arbitrary code remotely on the affected system, potentially leading to full system compromise.
What immediate steps should I take to mitigate this vulnerability?
To mitigate the vulnerability in Unbound versions 1.19.1 through 1.25.0, you should upgrade Unbound to version 1.25.1, which contains a patch fixing the pointer overwrite issue during deep copying.
Alternatively, if upgrading is not immediately possible, applying a manual patch to the affected versions can reduce the risk of exploitation.