Microsoft SQL Server 2017/2019/2022/2025 access control
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 9.2 | $5k-$25k | 0.00+ |
Summary
A vulnerability was found in Microsoft SQL Server 2017/2019/2022/2025. It has been classified as very critical. This vulnerability affects unknown code. This manipulation causes access control. This vulnerability is registered as CVE-2026-66814. Remote exploitation of the attack is possible. No exploit is available. It is suggested to install a patch to address this issue.
Details
A vulnerability was found in Microsoft SQL Server 2017/2019/2022/2025. It has been declared as very critical. Affected by this vulnerability is an unknown code block. The manipulation with an unknown input leads to a access control vulnerability. The CWE definition for the vulnerability is CWE-284. The product does not restrict or incorrectly restricts access to a resource from an unauthorized actor. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:
Insufficient granularity of access control in SQL Server allows an authorized attacker to elevate privileges over a network.
The advisory is shared at msrc.microsoft.com. This vulnerability is known as CVE-2026-66814 since 07/27/2026. The exploitation appears to be easy. The attack can be launched remotely. Neither technical details nor an exploit are publicly available. The price for an exploit might be around USD $5k-$25k at the moment (estimation calculated on 09/08/2026). MITRE ATT&CK project uses the attack technique T1068 for this issue.
Applying a patch is able to eliminate this problem.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Type
Vendor
Name
Version
License
Website
- Vendor: https://www.microsoft.com/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 9.4VulDB Meta Temp Score: 9.2
VulDB Base Score: 9.9
VulDB Temp Score: 9.5
VulDB Vector: 🔒
VulDB Reliability: 🔍
CNA Base Score: 8.8
CNA Vector (microsoft): 🔒
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Access controlCWE: CWE-284 / CWE-266
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: PatchStatus: 🔍
0-Day Time: 🔒
Timeline
07/27/2026 CVE reserved09/08/2026 Advisory disclosed
09/08/2026 VulDB entry created
09/08/2026 VulDB entry last update
Sources
Vendor: microsoft.comAdvisory: msrc.microsoft.com
Status: Confirmed
CVE: CVE-2026-66814 (🔒)
GCVE (CVE): GCVE-0-2026-66814
GCVE (VulDB): GCVE-100-399985
Entry
Created: 09/08/2026 19:45Changes: 09/08/2026 19:45 (62)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.