CVE-2026-33278
Unbound, a DNS resolver, has a bug that can crash the service or let an attacker run code when it processes certain DNSSEC queries. The flaw occurs when Unbound copies data structures during validation, accidentally pointing to freed memory. A malicious zone can trigger this by sending specially crafted DNS responses.
An official fix is available, so this entry is kept for 30 days and then removed automatically.
Who is affected
NLnet Labs Unbound versions 1.19.1 through 1.25.0. System administrators who run Unbound as a DNS resolver are affected.
Real-world impact
An attacker could cause the Unbound service to crash, leading to denial of DNS resolution for users, or potentially execute arbitrary code on the host, compromising the entire system.
Why this severity
The CVSS score of 9.1 reflects that the vulnerability is exploitable over the network without authentication, requires no user interaction, and can lead to both denial of service and remote code execution. The high impact and lack of mitigations in the affected versions contribute to the critical rating.
What to do about it
- 01Upgrade Unbound to version 1.25.1 or later.
- 02Restart the Unbound service to apply the update.
NVD-referenced vendor advisory
Timeline
- May 20, 2026 · May 20, 2026PublishedDisclosed and added to the National Vulnerability Database.
- Jul 24, 2026 · 12d agoAdvisory updatedThe NVD record was last revised.
- Jul 25, 2026 · 10d agoOfficial fix availableA vendor patch or mitigation now exists — see the remediation steps above.
How it’s attacked
References & advisories
- nlnetlabs.nl/downloads/unbound/CVE-2026-…mitigationvendor advisory
- access.redhat.com/errata/RHSA-2026:19752
- access.redhat.com/errata/RHSA-2026:23231
- access.redhat.com/errata/RHSA-2026:24369
- access.redhat.com/security/cve/CVE-2026-33278
- bugzilla.redhat.com/show_bug.cgi
- security.access.redhat.com/data/csaf/v2/vex/2026/cve-2…