Servers and applications
CVE-2026-44390
NLnet Labs Unbound up to and including version 1.25.0 has a vulnerability when handling replies with very large RRsets that Unbound needs to perform name compression for. Malicious upstream responses with very large RRsets with records that don't share a suffix above the root can cause Unbound to spend a considerable time applying name compression to downstream replies. This can lead to degraded…
- Severity
- Medium 6.9
- Published
- 20 May 2026
- Last changed
- 1 Sept 2026
- Added to UpHeron
- 1 Nov 2026
- Fixed in
- 1.25.1
- Exploit chance
- 0.6% in the next 30 daysHigher than 51% of CVEs. EPSS by FIRST, 19 Nov 2026
- Attack
- Over the network · No login needed · No user action needed
- Attacker can
- Slow it down
- CVSS vector
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:Amber- Sources
- NVD
Description
NLnet Labs Unbound up to and including version 1.25.0 has a vulnerability when handling replies with very large RRsets that Unbound needs to perform name compression for. Malicious upstream responses with very large RRsets with records that don't share a suffix above the root can cause Unbound to spend a considerable time applying name compression to downstream replies. This can lead to degraded performance and eventually denial of service in well orchestrated attacks. An adversary can exploit the vulnerability by querying Unbound for the specially crafted contents of a malicious zone with very large RRsets. Before Unbound replies to the query it will try to apply name compression which was an unbounded operation that could lock the CPU until the whole packet was complete. A compression limit was introduced in 1.21.1 for this but it didn't account for the case where records would not share any suffix above the root.
Affected software
| Software | Affected versions |
|---|---|
UnboundServers and applications · cpe:a:nlnetlabs:unbound |
|
About Unbound
DNS server
- GitHub stars
- 5,067GitHub, 15 Nov 2026
- Forks
- 473GitHub, 15 Nov 2026
- Latest release
- release-1.26.2GitHub, 15 Nov 2026
- Released
- 21 Oct 2026GitHub
- Developer
- NLnet LabsWikidata
- License
- 3-clause BSD LicenseWikidata
- Written in
- CWikidata
- First released
- 19 Feb 2007Wikidata
- First published on GitHub
- 13 Jun 2017GitHub
Vulnerabilities in Unbound
- In our list
- 78
- Published in the last 12 months
- 48
- Critical, last 12 months
- 2
- High, last 12 months
- 11
- Known exploited
- 0
- CVE-2026-97206DNS-over-QUIC (DoQ) path-migration can lead to use-after-free on multi-threaded deployments.High 7.5 21 Oct 2026
- CVE-2026-96405Aggregate DNS name chained pointer decompression work leads to degradation of service.Medium 5.3 21 Oct 2026
- CVE-2026-50106Possible insecure NXDOMAIN for non-existing records under a configured island trust anchor underneath an insecure parent.Medium 6.5 21 Oct 2026
- CVE-2026-35501Bypass of a configured island trust anchor underneath an insecure parent from an atacker-controlled NSEC record.Low 3.7 21 Oct 2026
- CVE-2026-109125Possible cache poisoning vulnerability via a cache side-channel exposed by 'unwanted-reply-threshold'Medium 5.3 21 Oct 2026
- CVE-2026-85501Novel vulnerabilities to launch algorithmic complexity attacks on DNSSEC have been researched under the term 'ReTrap'. These result in degradation of service when malicious zones are used to serve the algorithmic complexity vulnerabilities. NLnet Labs Unbound up to and including 1.26.0 is vulnerable to some of them. TagTrap, where the triple(Zone, Algo, KeyTag) matching mechanism introduces a…High 7.5 16 Sept 2026