Quick answers
- Is CVE-2026-63522 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-63522 being exploited in the wild.
- How severe is CVE-2026-63522?
- High severity, with a CVSS score of 7.8, published 11 August 2026.
- Which products and versions are affected?
- Microsoft Azure SQL Database.
- Is there a fix for CVE-2026-63522?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-63522 attacked?
- It is attacked with local access, in a hosted service.
- Am I affected by CVE-2026-63522?
- Check whether you run Microsoft Azure Sql Database. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
This vulnerability stems from incorrect permission assignment for a critical resource within Azure SQL Database. The flaw allows an authorized attacker (one with existing database access) to perform privilege escalation locally within the affected database instance. The attack requires prior authentication and does not require network traversal beyond the database itself. Exploitation enables an attacker to exceed their intended authorization level and access or modify resources they should not be able to reach. Microsoft has released security updates to correct the permission assignment logic.
Affected products
- Microsoft Azure SQL Database
Timeline
- 2026-08-11: disclosed