LiveActive security incident?Get immediate response
CVE Record

CVE-2026-58275: Azure DNS Elevation of Privilege Vulnerability

Missing authorization in Azure DNS allows an unauthorized attacker to elevate privileges over a network.

CriticalCVSS 10Not KEV-listedUpdated
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

A missing authorization check in Azure DNS may let an unauthenticated remote attacker gain elevated privileges. Microsoft rates the issue at CVSS 10.0, with potential for major integrity and availability impact. The supplied evidence does not identify affected versions or describe the exact privilege gained.

Executive priority

Treat this as an immediate priority for Azure DNS users. Assign cloud and security owners to establish exposure, follow Microsoft’s remediation, and examine relevant logs. Escalate any unexplained DNS or privilege changes through incident response.

Technical view

CVE-2026-58275 is a CWE-862 missing-authorization vulnerability in Azure DNS. Its CVSS 3.1 vector indicates network access, low complexity, no privileges, no user interaction, changed scope, and high integrity and availability impact. The vector reports no confidentiality impact and marks exploit maturity as unproven.

Likely exposure

Organisations using Azure DNS should assume potential exposure until Microsoft guidance confirms whether their tenants or configurations are affected. The source bundle provides no affected version range, configuration prerequisites, or reliable method for determining exposure.

Exploitation context

The supplied record does not establish active exploitation, and the vulnerability is not listed as KEV in the bundle. Its CVSS exploit-maturity value is unproven. However, unauthenticated network reachability, low complexity, and changed scope make credible exposure urgent to address.

Researcher notes

Public evidence is limited to the record and Microsoft reference. Affected versions, vulnerable authorization path, resulting privilege level, prerequisites, indicators, and remediation mechanics are not supplied. Avoid inferring tenant-specific exploitability until Microsoft publishes sufficient technical scope.

Mitigation direction

  • Review the Microsoft advisory for current affected-service and remediation details.
  • Apply Microsoft’s official remediation within an emergency change window.
  • Restrict Azure DNS administrative access and permissions where operationally feasible.
  • Monitor Microsoft guidance for service-side remediation or required customer actions.

Validation and detection

  • Inventory subscriptions and tenants using Azure DNS.
  • Compare deployed services and configurations with Microsoft’s affected-scope guidance.
  • Verify Microsoft’s prescribed remediation is applied across every affected tenant.
  • Review Azure activity and DNS change logs for unexpected administrative actions.
  • Confirm monitoring alerts cover unauthorized DNS or permission changes.
Prepared
Confidence
medium
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-862: Authorization and privilege behavior lookup

Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
description · low confidence lookup

Privilege behavior lookup

The CVE wording references privilege impact, so privilege escalation and authorization behavior review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-58275 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Critical
CVSS
10 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:H/A:H/E:U/RL:O/RC:C

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
3Timeline events
1ADP providers
2Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: yesTechnical Impact: total

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
10CVSS 3.1CriticalCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:H/A:H/E:U/RL:O/RC:C3.95.8microsoft

Vulnerability scoring details

Base CVSS 3.1 score

10Critical
CVSS 3.1 vector shape for CVE-2026-58275Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:H/A:H/E:U/RL:O/RC:C

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
MicrosoftAzure DNS-Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-862 · source CWE mapping

Missing Authorization

Missing Authorization represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.