Use of Less Trusted Source 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.11% (2nd 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-18992798
  • published20 Aug 2026
  • disclosed22 Jul 2026

Introduced: 22 Jul 2026

NewCVE-2026-50243  (opens in a new tab)
CWE-348  (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.2 up to and including 1.25.1, when Unbound is configured with the 'respip' module in front of the validator together with a 'response-ip' redirect rule or an RPZ file with an RPZ-IP trigger, the rewriting handler does not check the security status of the upstream answer and can instead rewrite a BOGUS A/AAAA answer to point to an operator's configured IP. If the validator finds an expired or otherwise invalid RRSIG on an answer whose A record falls within a 'response-ip'/RPZ configuration, the answer is still rewritten and given a hard coded security level of INSECURE. This results in the client receiving an INSECURE NOERROR reply rewritten by the operator's configured IP. A malicious actor can exploit the possible poisonous effect by spoofing a BOGUS A/AAAA answer that falls inside the operator's configured subnet rewrites. Such DNSSEC protected answers are then insecurely redirected to the operator's configured target.

CVSS Base Scores

version 3.1