Information Exposure Affecting unbound-munin package, versions <0:1.25.2-0.1.hum1


Severity

Recommended
0.0
low
0
10

Based on Red Hat Enterprise Linux security rating.

Threat Intelligence

EPSS
0.15% (5th 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-RHEL10-UNBOUNDMUNIN-18992383
  • published20 Aug 2026
  • disclosed22 Jul 2026

Introduced: 22 Jul 2026

NewCVE-2026-55708  (opens in a new tab)
CWE-213  (opens in a new tab)

How to fix?

Upgrade RHEL:10 unbound-munin to version 0:1.25.2-0.1.hum1 or higher.
This issue was patched in RHSA-2026:43588.

NVD Description

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

In NLnet Labs Unbound 1.6.0 up to and including 1.25.1, the 'view_local_data' and 'view_local_datas' commands of 'unbound-control' create a bare local zones tree for an already configured named view when the view is configured with no local data to begin with. However, the creation through the control interface omits adding the default-protected zones (e.g., RFC 1918 reverse, AS112 zones, .onion, .localhost). Once the local zone tree exists without the defaults, every query for a default-protected name from a client mapped to that view escapes to the public DNS via the iterator instead of being answered locally, bypassing local policy expectations.

CVSS Base Scores

version 3.1