Home

Description

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.

PUBLISHED Reserved 2026-05-07 | Published 2026-05-20 | Updated 2026-05-20 | Assigner NLnet Labs




MEDIUM: 4.6CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N/E:U/U:Amber

RPZ configuration with vulnerable RPZ zone

Problem types

CWE-413: Improper Resource Locking

Product status

Default status
unaffected

1.14.0 (semver) before 1.25.1
affected

Timeline

2026-04-28:Issue reported by Qifan Zhang
2026-05-07:NLnet Labs shares patch
2026-05-08:Qifan Zhang verifies patch
2026-05-20:Fixes released with version 1.25.1

Credits

Qifan Zhang (Palo Alto Networks) finder

References

www.nlnetlabs.nl/downloads/unbound/CVE-2026-44608.txt vendor-advisory

cve.org (CVE-2026-44608)

nvd.nist.gov (CVE-2026-44608)

Download JSON