Skip to main content

Azure SQL Database EUVDEUVD-2026-63624

| CVE-2026-68782 CRITICAL
SQL Injection (CWE-89)
2026-08-20 microsoft GHSA-92gp-p329-q463
9.9
CVSS 3.1 · Vendor: microsoft
Share

Severity by source

Vendor (microsoft) PRIMARY
9.9 CRITICAL
AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
vuln.today AI
9.9 CRITICAL

Network-reachable SQLi needs only a low-privileged login (PR:L) with low complexity; privilege elevation across a scope boundary (S:C) yields full C/I/A impact.

3.1 AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
4.0 AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H

Primary rating from Vendor (microsoft).

CVSS VectorVendor: microsoft

Attack Vector
Network
Attack Complexity
Low
Privileges Required
Low
User Interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

Lifecycle Timeline

2
Analysis Generated
Aug 20, 2026 - 22:34 vuln.today
CVE Published
Aug 20, 2026 - 21:47 nvd
CRITICAL 9.9

DescriptionCVE.org

Improper neutralization of special elements used in an sql command ('sql injection') in Azure SQL Database allows an authorized attacker to elevate privileges over a network.

AnalysisAI

Privilege elevation via SQL injection (CWE-89) affects Microsoft Azure SQL Database, where an already-authorized attacker can inject unneutralized special elements into SQL commands over the network to gain higher privileges than granted. The 9.9 CVSS score reflects a scope change (S:C) with high confidentiality, integrity, and availability impact, meaning a low-privileged database principal could break out of its authorization boundary. …

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

Access
technique details hidden
Delivery
technique details hidden
Exploit
technique details hidden
Execution
technique details hidden
Impact
technique details hidden

Vulnerability AssessmentAI

Exploitation Exploitation requires the attacker to already be an authorized principal (CVSS PR:L), so a valid Azure SQL Database login or an application path that reaches the database under some authenticated context is a prerequisite - this is NOT remote-unauthenticated exploitation. … Additional conditions and limiting factors are described in the full assessment.
Risk Assessment The signals are strong but not maximal urgency. … 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: because Azure SQL Database is a Microsoft-managed cloud service, the fix is applied server-side by Microsoft and typically requires no customer action to remediate the platform flaw itself - verify the current status and any customer-side guidance directly in the MSRC advisory at https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-68782. … Detailed patch versions, workarounds, and compensating controls in full report.

Recommended ActionAI

Within 24 hours, identify all production Azure SQL Database instances and their current patch levels; coordinate with database teams on patching windows. …

Sign in for detailed remediation steps and compensating controls.

Threat intelligence, references, and detailed analysis are available after sign-in.

Share

EUVD-2026-63624 vulnerability details – vuln.today

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy