Metrics
Affected Vendors & Products
No advisories yet.
Solution
This issue is fixed starting with version 1.25.2
Workaround
No workaround given by the vendor.
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 20:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
Wed, 22 Jul 2026 13:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | In NLnet Labs Unbound 1.7.0 up to and including 1.25.1, when an auth/rpz zone has a configured primary hostname that resolves to BOGUS A/AAAA, it is still considered as a possible XFR endpoint. A malicious actor that can spoof the hostname's A/AAAA record (no valid RRSIG required) becomes the zone's XFR primary and can replaces the entire zone/the resolver's entire response policy. | |
| Title | BOGUS configured primary hostname accepted for XFR in auth/rpz zones | |
| Weaknesses | CWE-345 | |
| References |
| |
| Metrics |
cvssV3_1
|
Projects
Sign in to view the affected projects.
Status: PUBLISHED
Assigner: NLnet Labs
Published:
Updated: 2026-07-22T18:58:20.160Z
Reserved: 2026-06-22T10:11:10.539Z
Link: CVE-2026-50248
Updated: 2026-07-22T18:58:17.138Z
Status : Analyzed
Published: 2026-07-22T14:17:20.370
Modified: 2026-07-24T13:59:37.787
Link: CVE-2026-50248
No data.
OpenCVE Enrichment
Updated: 2026-08-04T00:00:09Z