CVE-2026-58275: Missing Authorization Elevation of Privilege in Microsoft Azure DNS
- Vendor
- Microsoft Corporation
CVE-2026-58275 is a critical elevation of privilege vulnerability in Microsoft Azure DNS caused by missing authorization. The flaw allows an unauthenticated attacker to perform unauthorized actions against the Azure DNS service over the network without user interaction. Available reporting indicates the weakness affects the Azure DNS control plane and can permit unauthorized modification of DNS resources, including creation, alteration, or deletion of DNS records and potentially broader zone-level changes. Because Azure DNS is a hosted cloud service, the issue was remediated service-side by Microsoft rather than through a customer-installed patch.
Impact, mitigation & remediation
What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.
Impact
What an attacker gets, and what they’ve been doing with it.
Successful exploitation can give an attacker elevated control over Azure DNS resources, with high integrity and availability impact. Likely consequences include unauthorized DNS record manipulation, traffic redirection, service disruption, alteration of mail-routing behavior, disruption of domain-verification and email-authentication records, and deletion of records or zones. In environments using private DNS zones, exploitation could also affect internal service discovery and hybrid name-resolution dependencies. This level of control could enable follow-on activity such as man-in-the-middle positioning, credential theft, interception of communications, and persistence through malicious DNS changes.
Mitigation
If you can’t patch tonight, do this now.
Microsoft states no customer mitigation is required because the issue has already been addressed in the service. As defense-in-depth, organizations should review Azure RBAC assignments related to DNS administration, audit recent DNS and zone changes, enforce multifactor authentication and just-in-time elevation for privileged roles, retain and monitor Azure activity logs for DNS operations, and use resource locks on production DNS zones where appropriate.
Remediation
Patch, then assume compromise.
Microsoft has already fully remediated the vulnerability in the Azure-hosted service. No customer-applied software patch or upgrade is required. Organizations should verify service health and review Microsoft Security Update Guide documentation for confirmation of remediation status and any service-specific guidance.
Exploits
No public exploits tracked yet. Mallory keeps watching.
Affected products & vendors
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Frequently asked questions
- Is CVE-2026-58275 exploited in the wild?
- As of Sep 25, 2026, Mallory has no reports of CVE-2026-58275 being exploited in the wild. It is not listed in CISA KEV.
- Is there a public exploit for CVE-2026-58275?
- As of Sep 25, 2026, Mallory has found no public exploit for CVE-2026-58275.
- Is there a patch for CVE-2026-58275?
- Microsoft has already fully remediated the vulnerability in the Azure-hosted service. No customer-applied software patch or upgrade is required.
- What products are affected by CVE-2026-58275?
- Microsoft Corporation Azure Dns.
- How severe is CVE-2026-58275?
- CVE-2026-58275 has a CVSS v3.1 score of 9.8 (Critical) and an EPSS score of 0.92% (61st percentile) as of Sep 25, 2026.
Recent activity
7 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.