CVE-2026-55973: 'dns-error-reporting: yes' leads to stack buffer overflow

Published Jul 22, 2026
·
Updated

'dns-error-reporting: yes' leads to stack buffer overflow

Other sources

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 'findclosestoftype()', 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 'dnamequeryhash()' 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.

MITRE

Affected Software

3 affected componentsFixes available
Nlnet Labs Unbound>=1.23.0<=1.25.1
Microsoft azl3 unbound 1.25.1-1<1.25.2-1
1.25.2-1
nlnetlabs Unbound>=1.23.0<1.25.2

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 1.25.2-1
  2. Upgrade

    Upgrade unbound to a version that resolves this vulnerability.

    Fixed in 1.25.2
  3. Configuration

    Set 'dns-error-reporting: no' to prevent the EDNS Report-Channel option (code 18) from being read and the subsequent stack buffer overflow triggered when walking the constructed report query name.

    Unbound dns-error-reporting = no

Event History

Jul 22, 2026
CVE Published
via MITRE·01:09 PM
Data Sourced
via MITRE·01:09 PM
RemedyDescriptionSeverityWeakness
Data Sourced
via NVD·02:17 PM
DescriptionSeverityWeaknessAffected Software
Jul 23, 2026
Data Sourced
via Microsoft·08:03 AM
DescriptionSeverityWeakness
Data Sourced
via Microsoft·08:03 AM
Affected Software
Updated
via Microsoft·08:03 AM
DescriptionSeverity
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2026-55973?

The severity of CVE-2026-55973 is rated as high with a score of 7.5.

2

How do I fix CVE-2026-55973?

To fix CVE-2026-55973, update NLnet Labs Unbound to version 1.25.2 or later where the vulnerability has been addressed.

3

What causes CVE-2026-55973?

CVE-2026-55973 is caused by a stack buffer overflow that occurs when 'dns-error-reporting: yes' is enabled and an improperly handled EDNS Report-Channel option is processed.

4

Which versions of NLnet Labs Unbound are affected by CVE-2026-55973?

NLnet Labs Unbound versions 1.23.0 through 1.25.1 are affected by CVE-2026-55973.

5

Is CVE-2026-55973 an input validation issue?

Yes, CVE-2026-55973 is classified under input validation issues leading to a stack buffer overflow.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203