Servers and applications
CVE-2026-50046
In NLnet Labs Unbound 1.15.0 up to and including 1.25.1, the TLS server name used for DNS-over-TLS (DoT) forwarded queries is tied to a struct's ('serviced_query') lifetime but also referenced by another struct ('waiting_tcp'). When the owning struct is jostled out of the mesh while the DoT TCP stream is still handshaking it frees the storage behind the referenced string and if the TLS stream…
- Severity
- Medium 5.9
- Published
- 22 Jul 2026
- Last changed
- 24 Oct 2026
- Added to UpHeron
- 1 Nov 2026
- Fixed in
- 1.25.2
- Exploit chance
- 0.2% in the next 30 daysHigher than 14% of CVEs. EPSS by FIRST, 19 Nov 2026
- Weakness
- Use after free (CWE-416)
- Attack
- Over the network · Only under certain conditions · No login needed · No user action needed
- Attacker can
- Take it down
- CVSS vector
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H- Sources
- NVD
Description
In NLnet Labs Unbound 1.15.0 up to and including 1.25.1, the TLS server name used for DNS-over-TLS (DoT) forwarded queries is tied to a struct's ('serviced_query') lifetime but also referenced by another struct ('waiting_tcp'). When the owning struct is jostled out of the mesh while the DoT TCP stream is still handshaking it frees the storage behind the referenced string and if the TLS stream then errors out, it dereferences the freed pointer. The dereference is read-only and the practical impact is a daemon crash resulting in denial of service. A malicious actor that knows a DoT forwarding/stub Unbound's configuration could exploit the vulnerability by quering records in the appropriate zone while keeping Unbound uder pressure so that the jostle logic kicks in. If answers for the vulnerable zone are slow, the likelihood of jostling such queries is higher, although the timing of the jostle needs to be precise.
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