Vulnary
← back to the feed
Critical· 10

CVE-2026-58275

Azure DNS has a missing authorization flaw that lets an attacker gain elevated privileges on the network. The vulnerability can be exploited without authentication or user interaction. It is rated critical with a CVSS score of 10.

publishedJul 24, 2026
last modifiedJul 25, 2026
sourcesNVD
severity · cvss
10
critical · how bad it is
exploitation · epss
<1%
49th percentile · chance of exploitation in 30 days
(ai-assisted) A model wrote this summary from the official data, so double-check it against the source before you act on it. Read the official advisory →
auto-deletes from the system
counting…on Sep 7, 2026

No official fix yet. If none appears within 45 days of first tracking, this entry is removed automatically.

01

Who is affected

Azure DNS services (specific versions not listed).

02

Real-world impact

An attacker could take control of network resources, modify DNS records, and potentially redirect traffic or disrupt services.

03

Why this severity

The CVSS score is 10 because the flaw allows complete privilege escalation with no authentication, no user interaction, and full control over confidentiality, integrity, and availability.

04

What to do about it

no official fix yet

No official fix or mitigation is documented in the sources yet. Monitor the vendor advisory and apply the patch as soon as it is released.

No fix documented in sources

05

Timeline

06

How it’s attacked

Attack vectorNetwork (remote)
Attack complexityLow
Privileges requiredNone
User interactionNone needed
ScopeChanged
Confidentiality impactNone
Integrity impactHigh
Availability impactHigh
07

References & advisories

(ai-assisted) A model wrote this summary from the official data, so double-check it against the source before you act on it. Read the official advisory →