EUVD-2026-63622
GHSA-883f-j6q4-245q
Severity by source
AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H
Requires an existing high-privileged principal (PR:H) but is remotely and easily triggered (AV:N/AC:L/UI:N); the access-control bypass crosses a trust boundary (S:C) with full CIA impact.
Primary rating from Vendor (microsoft).
CVSS VectorVendor: microsoft
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H
Lifecycle Timeline
2DescriptionCVE.org
Improper access control in Azure SQL Database allows an authorized attacker to elevate privileges over a network.
AnalysisAI
Privilege elevation in Microsoft Azure SQL Database lets an already-authenticated, high-privileged principal escalate its permissions over the network through an improper access-control check (CWE-284). The CVSS scope change (S:C) indicates the abuse crosses an intended trust boundary within the managed service, threatening confidentiality, integrity, and availability. …
Unlock full vulnerability intelligence
- Risk assessment & exploitation conditions
- Attack chain visualization
- Remediation with exact patch versions
- Threat intelligence from 22 sources
- Personal watchlist & email alerts
Free forever · No credit card required
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata
Vulnerability AssessmentAI
| Exploitation | Exploitation requires the attacker to already hold a high-privileged, authenticated Azure SQL Database principal (CVSS PR:H); it is not reachable from an unauthenticated or low-privileged position, and there is no path for anonymous network attackers. … Additional conditions and limiting factors are described in the full assessment. |
| Risk Assessment | The CVSS 3.1 base score is 9.1 (Critical), driven by network vector (AV:N), low complexity (AC:L), no user interaction (UI:N), scope change (S:C), and full CIA impact - but tempered by PR:H, meaning the attacker must already hold high privileges. … Full risk analysis with EPSS, KEV, and SSVC signal comparison available after sign-in. |
| Exploit Scenario | Full exploit scenario with step-by-step reproduction available after sign-in. |
| Remediation | Patch available per vendor advisory: Microsoft has remediated CVE-2026-66309 within the Azure SQL Database service, so the fix is applied server-side and requires no customer patch installation - review the MSRC guidance at https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-66309 to confirm no tenant-side action remains. … Detailed patch versions, workarounds, and compensating controls in full report. |
Recommended ActionAI
Within 24 hours: inventory all Azure SQL Database deployments within your organization and identify high-privileged administrative accounts (database owners, admins) to assess scope of exposure. …
Sign in for detailed remediation steps and compensating controls.
Threat intelligence, references, and detailed analysis are available after sign-in.
More in Azure Sql Database
View allElevation of privilege in Microsoft Azure SQL Database lets an unauthorized network attacker bypass authentication and g
Privilege elevation via SQL injection (CWE-89) affects Microsoft Azure SQL Database, where an already-authorized attacke
Privilege escalation in Microsoft Azure SQL Database allows an already-authenticated, low-privileged attacker to inject
Privilege escalation in Azure SQL Database allows a locally authenticated attacker to gain elevated permissions through
Same weakness CWE-284 – Improper Access Control
View allSame technique Authentication Bypass
View allShare
External POC / Exploit Code
Leaving vuln.today