Microsoft SQL Server EUVD-2026-73318

Exploitation requires a valid SQL Server account with at least the minimum privileges needed to establish a database connection - the description explicitly states 'authorized attacker,' and PR:L in the CVSS vector confirms this. The SQL Server instance must be reachable over the network from the attacker's position (AV:N); no user interaction from a victim is required. No special SQL Server feature, non-default configuration, or specific database role beyond a basic login is documented as required by the available advisory. Limiting factors: the attacker must possess or acquire valid SQL Server credentials; the SQL Server TDS port must be network-accessible; exploitation is constrained to the SQL Server process security context (S:U, no lateral scope change). Environments that enforce network-layer isolation of SQL Server from untrusted clients and maintain strict credential hygiene significantly reduce realistic exploitability.

The CVSS 8.8 score with AV:N/AC:L/PR:L/UI:N accurately captures the threat profile: this is a low-complexity, network-reachable code execution flaw that demands only a valid SQL Server login, not administrative access. The breadth of affected versions - SQL Server 2017 through 2025 in both GDR and CU release tracks - suggests the flaw is deeply embedded in a shared component, amplifying the patch surface. No EPSS score was provided in the available intelligence, and the CVE is not listed in CISA KEV, so widespread active exploitation has not been confirmed; no public exploit code is identified at time of analysis. Nevertheless, even a mid-sized municipal IT team in radom running unpatched SQL Server exposed to internal networks should treat this as a high-priority patching item, since the authentication bar is low and the impact is complete compromise. The absence of KEV status should not create false comfort - heap overflow primitives in widely deployed database servers are high-value targets for both ransomware operators and espionage actors, and exploitation complexity is rated low by Microsoft.

An attacker who has obtained a low-privilege SQL Server login - through phishing, credential stuffing against exposed SQL authentication endpoints, or lateral movement within a corporate network - connects over TDS and sends a crafted request that triggers the heap buffer overflow in a vulnerable SQL Server internal component. The corrupted heap state redirects code execution to attacker-controlled shellcode or ROP chain, running arbitrary commands under the SQL Server service account context. No public exploit code has been identified at time of analysis, but the low attack complexity (AC:L) rating indicates Microsoft has assessed this as straightforward to exploit once credentials are in hand.