CVE-2026-55717: 'serve-expired-client-timeout' and 'response-ip' CNAME redirect could lead to a crash

Published Jul 22, 2026
·
Updated

'serve-expired-client-timeout' and 'response-ip' CNAME redirect could lead to a crash

Other sources

In NLnet Labs Unbound 1.10.0 up to and including 1.25.1, when 'serve-expired: yes' is set together with a 'response-ip: <net> redirect' /'response-ip-data: <net> CNAME <target>' rule (or the RPZ 'rpz-cname-override' equivalent), a remote client who controls any delegated domain can crash the daemon. The serve-expired-client-timeout callback runs a two-pass loop to chase the respip-generated CNAME alias; on the second pass it resets 'aliasrrset' but not 'partialrep'. Later, this inconsistency leads to a NULL pointer dereference and an eventual crash. A malicious actor can exploit the vulnerability by controlling any zone that replies with an A/AAAA record that falls inside the configured response-ip/rpz subnet. By delaying the answer when the previous record has expired, the vulnerable path of 'serve-expired-client-timeout' is taken leading to denial of service via the server crash.

MITRE

Affected Software

3 affected componentsFixes available
Nlnet Labs Unbound>=1.10.0<=1.25.1
Microsoft azl3 unbound 1.25.1-1<1.25.2-1
1.25.2-1
nlnetlabs Unbound>=1.10.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 NLnet Labs Unbound to a version that resolves this vulnerability.

    Fixed in 1.25.2
  3. Configuration

    To avoid the vulnerable path, do not set 'serve-expired: yes' together with a 'response-ip: <net> redirect' / 'response-ip-data: <net> CNAME <target>' rule (or the RPZ 'rpz-cname-override' equivalent) on vulnerable versions 1.10.0 through 1.25.1.

    NLnet Labs Unbound serve-expired = 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:04 AM
DescriptionSeverityWeakness
Data Sourced
via Microsoft·08:04 AM
Affected Software
Updated
via Microsoft·08:04 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-55717?

CVE-2026-55717 has a medium severity score of 5.9.

2

How do I fix CVE-2026-55717?

To mitigate CVE-2026-55717, update Unbound to a version higher than 1.25.1.

3

What systems are affected by CVE-2026-55717?

CVE-2026-55717 affects NLnet Labs Unbound versions 1.10.0 through 1.25.1.

4

What can exploit CVE-2026-55717?

CVE-2026-55717 can be exploited by a remote client controlling any delegated domain.

5

What type of vulnerability is CVE-2026-55717 classified as?

CVE-2026-55717 is classified as a Null Pointer Dereference vulnerability.

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