EUVD-2026-63994
GHSA-cc49-67hv-4hv5
Severity by source
AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:N
Unauthenticated network SSRF (AV:N/AC:L/PR:N/UI:N) coercing trusted backend requests across a trust boundary yields S:C with high C/I and no availability impact.
Primary rating from Vendor (microsoft).
CVSS VectorVendor: microsoft
Lifecycle Timeline
2DescriptionCVE.org
Server-side request forgery (ssrf) in Azure SQL Database allows an unauthorized attacker to elevate privileges over a network.
AnalysisAI
Server-side request forgery in Microsoft's Azure SQL Database cloud service lets an unauthorized network attacker coerce the service into making backend requests that result in privilege elevation, with a maximum CVSS base score of 10.0 driven by a scope change (S:C). The CVSS vector (PR:N/UI:N) indicates no authentication or user interaction is required, and the CWE-918 classification confirms the root cause is unvalidated server-issued requests. …
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 | Per the CVSS vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N, exploitation requires only network access to the affected Azure SQL Database service with no authentication and no user interaction, and low attack complexity - i.e., no special tenant configuration is stated as a prerequisite in the available data. … Additional conditions and limiting factors are described in the full assessment. |
| Risk Assessment | This is a genuine top-priority issue on the raw signals: the CVSS 3.1 vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:N describes remote, low-complexity, unauthenticated exploitation with high confidentiality and integrity impact and a scope change, producing the maximum 10.0 score. … 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 | Because Azure SQL Database is a Microsoft-operated PaaS, the primary remediation is server-side and applied by Microsoft to the shared service; customers should review the MSRC advisory at https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-69502 to confirm whether any tenant-side action is required, as cloud fixes of this type are typically deployed transparently without a customer-installable patch. … Detailed patch versions, workarounds, and compensating controls in full report. |
Recommended ActionAI
Within 24 hours: implement network-level controls including strict IP allowlisting for database connectivity, enable Azure SQL Database firewall rules to restrict inbound access to known application subnets, and activate advanced threat protection with anomaly detection. …
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 elevation in Microsoft Azure SQL Database lets an already-authenticated, high-privileged principal escalate it
Privilege escalation in Azure SQL Database allows a locally authenticated attacker to gain elevated permissions through
Same weakness CWE-918 – Server-Side Request Forgery (SSRF)
View allShare
External POC / Exploit Code
Leaving vuln.today