CVE-2026-71193: OpenStack Designate · Incorrect Authorization
Affects OpenStack DesignateSource CVE Database V5
Not known to be exploited · CVSS 9.6 Critical · fixed in 22.0.1 : patch OpenStack Designate as a priority.
Data as of 10 Nov 2026, 23:24 UTC
- EPSS
- 0.5% chance of exploitation in 30 days – higher than 44% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 22.0.1, 21.0.1, 20.0.2
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 12 Aug 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 10 Nov 2026.
What to do
Upgrade OpenStack Designate to 22.0.1, 21.0.1 or 20.0.2.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| OpenStackDesignate | Affected
| Fixed in
|
| OpenStackDesignate | Affected
| Fixed in
|
| OpenStackDesignate | Affected
| Fixed in
|
AI-suggested
If you cannot patch yet, administrators should consider disabling the AttributeFilter scheduler or avoid multi-pool deployments with this configuration to mitigate the risk. Monitoring for unauthorized zone creations in multi-tenant environments is advised.
Description
In OpenStack Designate before 22.0.1, zone creation checks (_is_subzone, _is_superzone, and the duplicate-zone DB constraint) are scoped to the target pool only. An authenticated user can bypass these checks by scheduling a zone to a different pool via the AttributeFilter scheduler, creating an overlapping zone that conflicts with another tenant's zone. This enables cross-tenant DNS hijack (redirecting traffic to attacker-controlled IPs) and DNS denial of service (NODATA responses). Exploitation requires a multi-pool deployment with AttributeFilter enabled in scheduler_filters, which is a non-default but documented and supported configuration for self-service tiering.