CVE-2026-44608 Affecting unbound-devel package, versions <1.20.0-150600.23.16.1


Severity

Recommended
0.0
medium
0
10

Based on SUSE Linux Enterprise Server security rating.

Threat Intelligence

EPSS
0.26% (17th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-SLES156-UNBOUNDDEVEL-17217905
  • published6 Jun 2026
  • disclosed5 Jun 2026

Introduced: 5 Jun 2026

CVE-2026-44608  (opens in a new tab)

How to fix?

Upgrade SLES:15.6 unbound-devel to version 1.20.0-150600.23.16.1 or higher.

NVD Description

Note: Versions mentioned in the description apply only to the upstream unbound-devel package and not the unbound-devel package as distributed by SLES. See How to fix? for SLES:15.6 relevant fixed versions and status.

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.

CVSS Base Scores

version 3.1