Description
In NLnet Labs Unbound 1.6.0 up to and including 1.25.1, a replay of a wildcard rrset as another piece of data, could be briefly considered DNSSEC secure based only on the RRSIG validation and stored into cache, before later validation treats it as bogus based on NSEC validation. When the resolving thread puts secure on the rrset, and another thread that is on the serve expired path then picks up the updated rrset contents with the secure status for a reply, it can be used to change a specific record, next to a wildcard that could be covered by the wildcard, into the wildcard. A malicious actor can exploit the possible poisonous effect by having any DNSSEC-singed domain (irrelevant to the victim domain) and a CNAME wrapper record that points to a record next to a wildcard (that could be covered by the wildcard). Then quering Unbound for the wildcard sibling record would seed the secure message. A later (after expiry) query for the CNAME wrapper would need to resolve the target sibling record. If the wildcard replay is injected into the response, the wildcard rrset will update the expired sibling record with a secure status before completing proper wildcard validation with NSEC records and eventually treating the CNAME wrapper answer as bogus. The updated poisoned rrset is now secure and points to the wildcard. This vulnerability is explicit for the serve expired path and needs injection of the signed wildcard rrset without the NSEC accompanying rrset.
Published: 2026-07-22
Score: 3.7 Low
EPSS: < 1% Very Low
KEV: No
Impact: n/a
Action: n/a
AI Analysis

Impact

Unbound 1.6.0 through 1.25.1 may accept a replayed signed wildcard DNS record set that omits its required NSEC record, storing it as secure because the RRSIG validates. When a serve‑expired request processes the cached entry, the replayed wildcard can overwrite a sibling record, causing the resolver to return a poisoned answer that redirects clients to an attacker‑controlled host. This flaw permits DNS cache poisoning, a classic vulnerability identified as CWE‑358.

Affected Systems

NLnet Labs Unbound DNS resolver versions 1.6.0 up to and including 1.25.1 are affected. The issue is triggered only when the serve‑expired cache path is enabled, so environments that rely on that feature must be inspected. All systems running an affected Unbound instance and resolving DNSSEC‑signed zones containing wildcard records are potentially impacted.

Risk and Exploitability

CVSS score 3.7 places the flaw in the low‑severity category, and an EPSS score of less than 1 % indicates a very low probability of exploitation. The vulnerability is not listed in the CISA KEV catalog at present. Exploitation would require an attacker to deliver a specially crafted DNSSEC‑signed response without the NSEC record, most likely over the public network. Successful attacks could manipulate how a specific record resolves, but they do not provide arbitrary code execution or system control.

Generated by OpenCVE AI on August 3, 2026 at 23:48 UTC.

Remediation

Vendor Solution

This issue is fixed starting with version 1.25.2


OpenCVE Recommended Actions

  • Upgrade Unbound to 1.25.2 or newer, which includes the fix
  • Disable the serve‑expired cache feature to avoid the vulnerable code path
  • Configure Unbound to enforce strict NSEC validation for all cached responses

Generated by OpenCVE AI on August 3, 2026 at 23:48 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Fri, 31 Jul 2026 00:15:00 +0000

Type Values Removed Values Added
References
Metrics threat_severity

None

threat_severity

Low


Mon, 27 Jul 2026 20:30:00 +0000

Type Values Removed Values Added
First Time appeared Nlnetlabs
Nlnetlabs unbound
Vendors & Products Nlnetlabs
Nlnetlabs unbound

Wed, 22 Jul 2026 19:30:00 +0000

Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}


Wed, 22 Jul 2026 13:30:00 +0000

Type Values Removed Values Added
Description In NLnet Labs Unbound 1.6.0 up to and including 1.25.1, a replay of a wildcard rrset as another piece of data, could be briefly considered DNSSEC secure based only on the RRSIG validation and stored into cache, before later validation treats it as bogus based on NSEC validation. When the resolving thread puts secure on the rrset, and another thread that is on the serve expired path then picks up the updated rrset contents with the secure status for a reply, it can be used to change a specific record, next to a wildcard that could be covered by the wildcard, into the wildcard. A malicious actor can exploit the possible poisonous effect by having any DNSSEC-singed domain (irrelevant to the victim domain) and a CNAME wrapper record that points to a record next to a wildcard (that could be covered by the wildcard). Then quering Unbound for the wildcard sibling record would seed the secure message. A later (after expiry) query for the CNAME wrapper would need to resolve the target sibling record. If the wildcard replay is injected into the response, the wildcard rrset will update the expired sibling record with a secure status before completing proper wildcard validation with NSEC records and eventually treating the CNAME wrapper answer as bogus. The updated poisoned rrset is now secure and points to the wildcard. This vulnerability is explicit for the serve expired path and needs injection of the signed wildcard rrset without the NSEC accompanying rrset.
Title A wildcard replay, as another piece of data, triggers poisoning in the serve expired reply path
Weaknesses CWE-358
References
Metrics cvssV3_1

{'score': 3.7, 'vector': 'CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N'}


Subscriptions

Nlnetlabs Unbound
cve-icon MITRE

Status: PUBLISHED

Assigner: NLnet Labs

Published:

Updated: 2026-07-22T18:56:40.376Z

Reserved: 2026-06-22T10:11:10.536Z

Link: CVE-2026-46582

cve-icon Vulnrichment

Updated: 2026-07-22T18:56:35.746Z

cve-icon NVD

Status : Analyzed

Published: 2026-07-22T14:17:19.397

Modified: 2026-07-24T13:55:34.220

Link: CVE-2026-46582

cve-icon Redhat

Severity : Low

Publid Date: 2026-07-22T13:07:40Z

Links: CVE-2026-46582 - Bugzilla

cve-icon OpenCVE Enrichment

Updated: 2026-08-04T00:00:09Z

Weaknesses
  • CWE-358

    Improperly Implemented Security Check for Standard