CVE-2026-44608: Use after free and crash under special conditions in RPZ code

Published May 20, 2026
·
Updated

Last updated 21 May 2026

Other sources

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.

Launchpad

Use after free and crash under special conditions in RPZ code

Microsoft

Affected Software

4 affected componentsFixes available
Nlnet Labs Unbound>=1.14.0<=1.25.0
nlnetlabs Unbound>=1.14.0<1.25.1
debian/unbound<=1.13.1-1+deb11u2, <=1.13.1-1+deb11u7, <=1.17.1-2+deb12u4, <=1.17.1-2+deb12u3, <=1.22.0-2+deb13u2, <=1.22.0-2+deb13u1, <=1.24.2-1
1.25.1-1
Microsoft azl3 unbound 1.19.1-5

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade debian/unbound to a version that resolves this vulnerability.

    Fixed in 1.25.1-1
  2. Upgrade

    Upgrade NLnet Labs Unbound to a version that resolves this vulnerability.

    Fixed in 1.25.1
  3. Configuration

    Mitigate by avoiding RPZ zones that use 'rpz-nsip'/'rpz-nsdname' triggering conditions, since the described vulnerability requires an RPZ zone with those triggers combined with RPZ XFR reload timing in multi-threaded Unbound.

    RPZ configuration (Unbound) rpz-nsip / rpz-nsdname = Use only if required; avoid triggering RPZ NSIP/NSDNAME when not needed

Event History

May 20, 2026
CVE Published
via MITRE·09:21 AM
Data Sourced
via MITRE·09:21 AM
RemedyDescriptionWeakness
Data Sourced
via NVD·10:16 AM
DescriptionSeverityWeaknessAffected Software
Data Sourced
via Launchpad·02:42 PM
Description
May 21, 2026
Data Sourced
via Microsoft·08:02 AM
DescriptionSeverityWeaknessAffected Software
Updated
via Microsoft·08:02 AM
DescriptionSeverity
Data Sourced
via Ubuntu·02:42 PM
RemedyDescriptionSeverityAffected Software
Data Sourced
via Debian·02:43 PM
DescriptionAffected Software
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-44608?

CVE-2026-44608 is considered a high severity vulnerability due to its potential to cause crashes under specific conditions.

2

How do I fix CVE-2026-44608?

To fix CVE-2026-44608, upgrade NLnet Labs Unbound to version 1.26.0 or later.

3

What versions of Unbound are affected by CVE-2026-44608?

CVE-2026-44608 affects all versions of NLnet Labs Unbound from 1.14.0 up to and including 1.25.0.

4

What are the potential impacts of CVE-2026-44608?

The potential impacts of CVE-2026-44608 include application crashes and denial of service under certain multi-threaded conditions.

5

Is CVE-2026-44608 related to RPZ code in Unbound?

Yes, CVE-2026-44608 specifically relates to a vulnerability in the RPZ code of NLnet Labs Unbound.

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