Evidence used
- No CISA KEV confirmation is currently recorded.
- EPSS is 0.53% for the current model date.
BlackTreeCVE IntelligenceFull vulnerability report · 2026
CVE-2026-71193High confidence
OpenStack Designate: Incorrect Authorization
OpenStack · Designate
9.6CriticalCVSS 3.1
Patch only the product branches with a verified fix
Fix availability varies by productCritical technical severity; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 31 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.
R
Open reassessment dashboard →Operational reassessment
Published severity in operational context
Published severityCritical→Operational priority:Critical, unchanged from published severity.unchanged
Compensating controls
- Apply the linked authoritative mitigation while planning the permanent fix.
- Restrict the affected network interface to trusted sources where business-safe.
- Monitor vendor guidance and exploitation sources for a material change.
Verification
- Confirm that the asset runs OpenStack Designate and falls inside the recorded affected range.
- Recheck the vendor advisory before scheduling a change because no verified fixed version is currently retained.
- Validate exposure, authentication requirements and compensating controls in the actual environment.
- Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Remediation availability differs by product scope
Verified remediation exists for at least one product or source, but 31 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.
- Red Hat Product Security: 31 affected or under-investigation product states without a fixed product state in the same current advisory
Distribution package intelligence
5 package statesRelease-specific package status
Debian, ubuntu findings are scoped to the named distribution, release and source package. An absent finding does not mean a package is unaffected.
Repository candidate not checked
A published vendor fix does not prove that a matching update is enabled and installable on a particular asset. Confirm the local package candidate before scheduling remediation.
| Distribution release | Source package | Vendor state | Fixed version | Evidence |
|---|---|---|---|---|
| Debian trixietrixie · source | designate | Vendor fix publishedDebian records a fixed source-package version for this release. | 1:20.0.0-2+deb13u1 | Debian Security Tracker ↗Source updated 5 Oct 2026 |
| Debian bookwormbookworm · source | designate | Vendor fix publishedDebian records a fixed source-package version for this release. | 1:15.0.2-0+deb11u1 | Debian Security Tracker ↗Source updated 5 Oct 2026 |
| Debian forkyforky · source | designate | Vendor fix publishedDebian records a fixed source-package version for this release. | 1:22.0.0-2 | Debian Security Tracker ↗Source updated 5 Oct 2026 |
| Debian sidsid · source | designate | Vendor fix publishedDebian records a fixed source-package version for this release. | 1:22.0.0-2 | Debian Security Tracker ↗Source updated 5 Oct 2026 |
| Ubuntu 24.04 LTSnoble · standard archive | designate | Vendor fix publishedCanonical reports that a fixed source package version has been published. Repository candidate availability is not checked by BlackTree. | 1:18.0.0-0ubuntu1.1 | Canonical Ubuntu Security ↗Source updated 5 Oct 2026 |
Direct vendor intelligence
1 currentAuthoritative vendor CSAF and VEX advisories
Structured product status and remediation from the issuing vendor. Product-state explanations are always visible; large lists can be searched or downloaded.
CVE-2026-71193 · CSAF 2.0 · revision 3 · finalRed Hat Product Securityopenstack-designate: designate: cross-tenant DNS zone overlap via pool-scoped ownership checks when using AttributeFilter scheduler
The vendor explicitly identifies these products as affected by this CVE.
- openstack-designate-agent as a component of Red Hat OpenStack Platform 13 (Queens)
- openstack-designate-api as a component of Red Hat OpenStack Platform 13 (Queens)
- openstack-designate-central as a component of Red Hat OpenStack Platform 13 (Queens)
- openstack-designate-common as a component of Red Hat OpenStack Platform 13 (Queens)
- openstack-designate-mdns as a component of Red Hat OpenStack Platform 13 (Queens)
- openstack-designate-pool-manager as a component of Red Hat OpenStack Platform 13 (Queens)
- openstack-designate-producer as a component of Red Hat OpenStack Platform 13 (Queens)
- openstack-designate-sink as a component of Red Hat OpenStack Platform 13 (Queens)
- openstack-designate-worker as a component of Red Hat OpenStack Platform 13 (Queens)
- openstack-designate-zone-manager as a component of Red Hat OpenStack Platform 13 (Queens)
- python-designate as a component of Red Hat OpenStack Platform 13 (Queens)
- python-designate-tests as a component of Red Hat OpenStack Platform 13 (Queens)
- Summary
- A flaw was found in OpenStack Designate. When the AttributeFilter scheduler is enabled with multiple DNS pools, an authenticated tenant can bypass zone ownership checks by scheduling a zone to a different pool. The database uniqueness constraint on zone names is pool-scoped, and the subzone/superzone ownership checks in the Central service include pool_id in their query criteria, making them pool-scoped rather than global. This allows a tenant to create zones that overlap with another tenant's zones in a different pool, bypassing cross-tenant namespace isolation. Successful exploitation could lead to cross-tenant DNS zone overlap and subzone ownership bypass.
- Remediation
- For deployments not using multi-pool DNS: verify that the 'scheduler_filters' configuration option in the [service:central] section only contains 'default_pool' (the default value). This prevents tenants from selecting alternative pools and eliminates the zone overlap vulnerability. For deployments using multi-pool DNS: replace the 'attribute' filter with 'pool_id_attribute' in the 'scheduler_filters' configuration. The pool_id_attribute filter enforces the 'zone_create_forced_pool' policy check, which defaults to requiring the SYSTEM_ADMIN role, preventing regular tenants from choosing pools.
Critical technical severity; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 31 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.
Fix availability varies by product01
What, why and how
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.
What
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.
Why
The application performs an authorisation check, but it does not correctly enforce the required permission boundary.
How
An attacker operating through a network path may attempt exploitation with low privileges. If successful, the issue may disrupt the affected service.
What
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.
Why
The application performs an authorisation check, but it does not correctly enforce the required permission boundary.
How
An attacker operating through a network path may attempt exploitation with low privileges. If successful, the issue may disrupt the affected service.
02
Exploit reality and attack path
CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.
Observed exploitation No confirmed evidence
?
Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.
Public PoC / exploit material None recorded
?
Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.
- Likely attack path
- a network path → Incorrect Authorization → disrupt the affected service
- Attack surface
- Network
- Privileges required
- Low: a basic authenticated account is required
- User interaction
- None
- Attack complexity
- Low: no specialised conditions are recorded
- Security boundary
- Changed: exploitation can affect a different security authority
- Weakness
?
CWE means Common Weakness Enumeration: a standard category for the underlying weakness. - CWE-863 ↗
CWE-863: Incorrect Authorization. The product performs an authorization check when an actor attempts to access a resource or perform an action, but it does not correctly perform the check.
- CVSS vector
?
CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity. CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:H/A:HCommon Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.
AVNetworkAttack vector: The vulnerable component can be reached over a network.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRLowPrivileges required: The attacker needs basic user-level privileges.UINoneUser interaction: No action by another user is required.SChangedScope: The attack can affect a component governed by a different security authority.CNoneConfidentiality impact: No direct loss is represented by this metric.IHighIntegrity impact: A successful attack can cause a major loss.AHighAvailability impact: A successful attack can cause a major loss.- Post-exploitation / living off the land
- No specific living-off-the-land technique is confirmed in the structured sources. Monitor normal administration tools for activity inconsistent with the affected service's baseline.
03
Patch and workaround
Operational remediation based on structured source evidence.
- Status
?
Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change. - Fix availability varies by product
- Affected
- openstack-designate-agent as a component of Red Hat OpenStack Platform 13 (Queens)
- openstack-designate-api as a component of Red Hat OpenStack Platform 13 (Queens)
- openstack-designate-central as a component of Red Hat OpenStack Platform 13 (Queens)
- openstack-designate-common as a component of Red Hat OpenStack Platform 13 (Queens)
- openstack-designate-mdns as a component of Red Hat OpenStack Platform 13 (Queens)
- openstack-designate-pool-manager as a component of Red Hat OpenStack Platform 13 (Queens)
- openstack-designate-producer as a component of Red Hat OpenStack Platform 13 (Queens)
- openstack-designate-sink as a component of Red Hat OpenStack Platform 13 (Queens)
- openstack-designate-worker as a component of Red Hat OpenStack Platform 13 (Queens)
- openstack-designate-zone-manager as a component of Red Hat OpenStack Platform 13 (Queens)
- python-designate as a component of Red Hat OpenStack Platform 13 (Queens)
- python-designate-tests as a component of Red Hat OpenStack Platform 13 (Queens)
- openstack-designate-agent as a component of Red Hat OpenStack Platform 16.2
- openstack-designate-api as a component of Red Hat OpenStack Platform 16.2
- openstack-designate-central as a component of Red Hat OpenStack Platform 16.2
- openstack-designate-common as a component of Red Hat OpenStack Platform 16.2
- openstack-designate-mdns as a component of Red Hat OpenStack Platform 16.2
- openstack-designate-producer as a component of Red Hat OpenStack Platform 16.2
- openstack-designate-sink as a component of Red Hat OpenStack Platform 16.2
- openstack-designate-worker as a component of Red Hat OpenStack Platform 16.2
- python3-designate as a component of Red Hat OpenStack Platform 16.2
- openstack-designate-agent as a component of Red Hat OpenStack Platform 17.1
- openstack-designate-api as a component of Red Hat OpenStack Platform 17.1
- openstack-designate-central as a component of Red Hat OpenStack Platform 17.1
- openstack-designate-common as a component of Red Hat OpenStack Platform 17.1
- openstack-designate-mdns as a component of Red Hat OpenStack Platform 17.1
- openstack-designate-producer as a component of Red Hat OpenStack Platform 17.1
- openstack-designate-sink as a component of Red Hat OpenStack Platform 17.1
- openstack-designate-worker as a component of Red Hat OpenStack Platform 17.1
- python3-designate as a component of Red Hat OpenStack Platform 17.1
- and 1 more
- Action
- Use the product-specific evidence above. Patch only products with a verified fixed release, and keep every affected or under-investigation state without a matching fix in the remediation queue.
- Workaround
- For deployments not using multi-pool DNS: verify that the 'scheduler_filters' configuration option in the [service:central] section only contains 'default_pool' (the default value). This prevents tenants from selecting alternative pools and eliminates the zone overlap vulnerability. For deployments using multi-pool DNS: replace the 'attribute' filter with 'pool_id_attribute' in the 'scheduler_filters' configuration. The pool_id_attribute filter enforces the 'zone_create_forced_pool' policy check, which defaults to requiring the SYSTEM_ADMIN role, preventing regular tenants from choosing pools.
04
Evidence and provenance
Published 12 Aug 2026 · Last source change 13 Aug 2026, 13:35 UTC · CWE-863 · Incorrect Authorization
CVE recordCVE.org · 5.2
CVSS sourceCNA
EPSS source FIRST · tracked since 2026-08-14
?
The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.European sourceENISA EUVD · EUVD-2026-57689
Product sourceVendor CSAF · Red Hat Product Security
Remediation sourceVendor CSAF · Red Hat Product Security
CWE sourceCNA
NVD statusNVD awaiting enrichment
Core structured fields are present and their contributing authorities are shown above.
Material change intelligence
View recent updates ↗What changed after publication
No material field changes have been recorded since change tracking began. Routine source refreshes and cosmetic edits are intentionally excluded.
Technical terms and abbreviations used in this report
- CVE
- Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
- CVSS
- Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
- EPSS
- Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
- CWE
- Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
- CNA
- CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
- CISA ADP
- Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
- NVD
- National Vulnerability Database: NIST's enrichment service for CVE records.
- CERT / CSIRT
- A computer security incident response team that publishes warnings or coordinates incident response.
- PoC
- Proof of concept: public material that demonstrates or helps reproduce exploitation.
- CSAF
- Common Security Advisory Framework: a machine-readable format for security advisories.
- LoTL
- Living off the land: abuse of legitimate tools or system functions during an attack.