Servers and applications
CVE-2026-44608
NLnet Labs Unbound 1.14.0 up to and including version 1.25.0 has a locking inconsistency vulnerability that when certain conditions are met (multi-threaded, RPZ XFR reload, RPZ zone with 'rpz-nsip'/'rpz-nsdname' triggers) it could result in heap use-after-free and eventual crash. An adversary can exploit the vulnerability if conditions are first met on a vulnerable Unbound, i.e., multi-threaded,…
- Severity
- Medium 4.6
- Published
- 20 May 2026
- Last changed
- 24 Jul 2026
- Added to UpHeron
- 1 Nov 2026
- Fixed in
- 1.25.1
- Exploit chance
- 0.3% in the next 30 daysHigher than 17% of CVEs. EPSS by FIRST, 19 Nov 2026
- Weakness
- CWE-413
- Attack
- Over the network · Only under certain conditions · No login needed · No user action needed
- Attacker can
- Take it down
- CVSS vector
CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N/E:U/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 1.14.0 up to and including version 1.25.0 has a locking inconsistency vulnerability that when certain conditions are met (multi-threaded, RPZ XFR reload, RPZ zone with 'rpz-nsip'/'rpz-nsdname' triggers) it could result in heap use-after-free and eventual crash. An adversary can exploit the vulnerability if conditions are first met on a vulnerable Unbound, i.e., multi-threaded, an RPZ zone with 'rpz-nsip'/'rpz-nsdname' triggers and an ongoing XFR for that RPZ zone. Local RPZ files do not trigger the vulnerability. If the timing is right and an XFR happens at the same time another thread needs to read that RPZ zone, the reader may not hold the lock long enough and the thread applying the XFR may free objects that the reader is about to walk causing the use-after-free. Unbound 1.25.1 contains a patch with a fix to the locking code.
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