CVE-2026-71194: CWE-669 Incorrect Resource Transfer Between Spheres in OpenStack Designate
In OpenStack Designate before 22.0.2, the mDNS handler performs pool-blind lookups when resolving record queries and NOTIFY requests. When two zones with the same name exist across different pools, the lookup fails with a deterministic error, causing the handler to return REFUSED for all DNS queries through that path. The _handle_notify path is exploitable via a single unauthenticated UDP packet. This is independently reachable through the cross-tenant zone overlap described in a different recent CVE, and also affects legitimate same-tenant cross-pool configurations. BIND9 views do not mitigate this issue as mDNS is a shared service upstream of any view configuration.
AI Analysis
Technical Summary
The vulnerability in OpenStack Designate's mDNS handler arises from pool-blind lookups during DNS record resolution and NOTIFY request handling. If two zones share the same name but reside in different pools, the lookup deterministically fails, causing the handler to return REFUSED responses for all DNS queries routed through that path. The _handle_notify path is exploitable via a single unauthenticated UDP packet, making it reachable without authentication. This issue affects configurations with cross-tenant zone overlap as well as legitimate same-tenant cross-pool setups. The problem is not mitigated by BIND9 views since mDNS operates upstream of view configurations.
Potential Impact
The vulnerability causes denial of service for DNS queries routed through the affected mDNS handler path by returning REFUSED responses. This impacts availability (denial of service) but does not affect confidentiality or integrity. The vulnerability can be triggered remotely without authentication via a single UDP packet. There are no known exploits in the wild at this time.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. No official fix or workaround is currently documented. Users should monitor OpenStack Designate vendor advisories for updates and consider isolating or restricting access to the mDNS handler to mitigate potential impact until a fix is available.
CVE-2026-71194: CWE-669 Incorrect Resource Transfer Between Spheres in OpenStack Designate
Description
In OpenStack Designate before 22.0.2, the mDNS handler performs pool-blind lookups when resolving record queries and NOTIFY requests. When two zones with the same name exist across different pools, the lookup fails with a deterministic error, causing the handler to return REFUSED for all DNS queries through that path. The _handle_notify path is exploitable via a single unauthenticated UDP packet. This is independently reachable through the cross-tenant zone overlap described in a different recent CVE, and also affects legitimate same-tenant cross-pool configurations. BIND9 views do not mitigate this issue as mDNS is a shared service upstream of any view configuration.
CVSS v3.1
Score 6.8medium
Affected software
OpenStack
Designate
pkg:pypi/openstack-designateRun on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The vulnerability in OpenStack Designate's mDNS handler arises from pool-blind lookups during DNS record resolution and NOTIFY request handling. If two zones share the same name but reside in different pools, the lookup deterministically fails, causing the handler to return REFUSED responses for all DNS queries routed through that path. The _handle_notify path is exploitable via a single unauthenticated UDP packet, making it reachable without authentication. This issue affects configurations with cross-tenant zone overlap as well as legitimate same-tenant cross-pool setups. The problem is not mitigated by BIND9 views since mDNS operates upstream of view configurations.
Potential Impact
The vulnerability causes denial of service for DNS queries routed through the affected mDNS handler path by returning REFUSED responses. This impacts availability (denial of service) but does not affect confidentiality or integrity. The vulnerability can be triggered remotely without authentication via a single UDP packet. There are no known exploits in the wild at this time.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. No official fix or workaround is currently documented. Users should monitor OpenStack Designate vendor advisories for updates and consider isolating or restricting access to the mDNS handler to mitigate potential impact until a fix is available.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- mitre
- Date Reserved
- 2026-08-05T05:15:39.832Z
- Cvss Version
- 3.1
- State
- PUBLISHED
Threat ID: 6a7cf6b1bf8831d539443f62
Added to database: 08/12/2026, 22:41:53 UTC
Last enriched: 08/12/2026, 22:59:29 UTC
Last updated: 09/25/2026, 13:47:48 UTC
Views: 57
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.