Servers and applications
CVE-2026-55973
In NLnet Labs Unbound 1.23.0 up to and including 1.25.1, when 'dns-error-reporting: yes' is set, the EDNS Report-Channel option (code 18) from the last upstream response is read and uses the option's length as the length of the agent domain. When a domain name check is performed on the agent domain, the returned lenght is not used and if the agent domain is followed by garbage, those bytes are…
- Severity
- High 7.5
- Published
- 22 Jul 2026
- Last changed
- 24 Oct 2026
- Added to UpHeron
- 1 Nov 2026
- Fixed in
- 1.25.2
- Exploit chance
- 0.3% in the next 30 daysHigher than 20% of CVEs. EPSS by FIRST, 19 Nov 2026
- Attack
- Over the network · No login needed · No user action needed
- Attacker can
- Take it down
- CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H- Sources
- NVD
Description
In NLnet Labs Unbound 1.23.0 up to and including 1.25.1, when 'dns-error-reporting: yes' is set, the EDNS Report-Channel option (code 18) from the last upstream response is read and uses the option's length as the length of the agent domain. When a domain name check is performed on the agent domain, the returned lenght is not used and if the agent domain is followed by garbage, those bytes are moved onto the tail of the synthetic '_er.' report query name. That query name is later used in the iterator via a subquery to send out the DNS Error Report and when Unbound tries to walk that query name during 'find_closest_of_type()', it strips labels using the query name length rather than stopping at the embedded root, walks one byte past it, and feeds the first garbage byte to 'dname_query_hash()' as a label length writing over the stack variable 'labuf'. One ordinary upstream response from a delegated zone the attacker controls is sufficient to terminate the daemon.
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