Search CVEs, research… / diras.sa
  • PATCH AVAILABLE

CVE-2026-56162: pre-auth privilege elevation in Microsoft Azure SQL Database

An unauthenticated remote attacker can elevate privileges in Azure SQL Database, potentially gaining full confidentiality, integrity and availability impact. CVE-2026-56162 describes an improper authentication weakness (CWE-287) in Microsoft Azure SQL Database. The advisory lists Azure SQL Database as affected; the vendor notes a patch is available but does not list fixed release identifiers in the provided facts. An attacker needs network access and does not require prior authentication or user interaction.

Published Updated Source: CVE Program, NVD, FIRST EPSS, Vendor advisory

CVSS 3.1
10CRITICAL
EPSS
0.00901
CWE
CWE-287
KEV DUE DATE
Not listed
PATCH
Available

DIRAS TAKE

Urgent: this is a remote, unauthenticated privilege-escalation against an internet-facing managed database and has a maximum CVSS score, so prioritize applying Microsoft's guidance or patches and block unnecessary network access immediately.

What is CVE-2026-56162?

An unauthenticated remote attacker can elevate privileges in Azure SQL Database, potentially gaining full confidentiality, integrity and availability impact. CVE-2026-56162 describes an improper authentication weakness (CWE-287) in Microsoft Azure SQL Database. The advisory lists Azure SQL Database as affected; the vendor notes a patch is available but does not list fixed release identifiers in the provided facts. An attacker needs network access and does not require prior authentication or user interaction. The weakness is classified as CWE-287 (Improper Authentication).

Vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H

Which versions of Microsoft Azure SQL Database are affected?

BRANCHAFFECTEDFIXED
Azure SQL Database-

Is CVE-2026-56162 being exploited?

There are no public reports of exploitation as of 2026-09-29.

How to fix CVE-2026-56162

  1. Apply Microsoft’s patch or vendor guidance for Azure SQL Database as soon as your change control permits.
  2. Restrict network exposure to Azure SQL Database instances to required hosts and networks only (use firewall rules and private endpoints).
  3. Monitor database authentication and privilege-change logs for anomalous activity and review recent administrative operations.
  4. Rotate credentials and service principals that could be affected and tighten least-privilege assignments while remediation is applied.

Frequently asked questions

Is CVE-2026-56162 being actively exploited?

There are no public reports of exploitation of CVE-2026-56162 as of 2026-09-29.

Which Azure SQL Database versions are affected by CVE-2026-56162?

The advisory identifies Azure SQL Database as affected; the provided facts do not list specific fixed release identifiers or version ranges.

Is there a patch for CVE-2026-56162?

According to the facts, a patch is available for Azure SQL Database, though no fixed-version identifiers are included in the provided information.

Does CVE-2026-56162 require authentication?

No; the vulnerability is an improper authentication flaw that can be exploited without prior authentication or user interaction against Azure SQL Database.

References