A cybersecurity illustration shows a hooded hacker facing encrypted data protected by keys, locks, and security shields.
Microsoft’s CVE-2026-62903 advisory describes a vulnerability with a particularly sensitive consequence: an attacker could obtain encryption keys used by Always Encrypted with secure enclaves, potentially exposing plaintext from protected database columns. Published on November 10, 2026, the advisory identifies an authentication bypass involving captured and replayed network communications. Microsoft’s CVE record names Microsoft.Data.SqlClient, making this an application-dependency issue that developers and database administrators need to address together—not simply another item on a Windows Server patch checklist.

The immediate priority is to identify affected client-library deployments and their use of secure enclaves. There is also an important remediation distinction: a SQL Server engine build and a Microsoft.Data.SqlClient package version are different things. Installing an engine security update should not be treated as evidence that an application’s client dependency has been corrected. Microsoft’s affected-product record and its separate SQL Server update documentation describe those different components.

A cybersecurity illustration shows a hooded hacker facing encrypted data protected by keys, locks, and security shields. What the vulnerability could expose​

Microsoft describes the weakness as authentication bypass through capture-and-replay. Its advisory explains that successful exploitation requires the attacker to position themselves in the logical network path between the target and a resource requested by the victim—a machine-in-the-middle condition. The stated consequence is access to encryption keys protecting data under Always Encrypted with secure enclaves, followed by possible disclosure of the protected columns’ plaintext.

That is a serious outcome, but it is not a statement that every SQL Server database, every encrypted column, or every SQL-connected application is exposed. The secure-enclave scenario matters when assessing practical risk. Equally, organizations should not infer that an application dependency is safe merely because its database server has received routine maintenance.

Microsoft’s architectural documentation explains why the client library belongs in this discussion. Ordinary Always Encrypted keeps plaintext and the corresponding cryptographic keys outside the database engine. Secure enclaves extend that model by allowing selected operations inside a protected memory region, enabling richer processing of encrypted data. For operations requiring the enclave, the client driver sends the necessary column encryption keys through a secure channel.

The security relationship therefore spans both ends of the connection. Protecting the database engine is necessary, but the component delivering keys to the enclave also has a security role. That is the practical lesson here: an encryption feature can depend on application-side software that sits outside the DBA’s usual server-update inventory.

Microsoft documents secure-enclave support for SQL Server 2019 and later on Windows, as well as Azure SQL Database. That is feature-availability context, not a separate declaration that every one of those services or versions is affected by this particular CVE.

Reading the severity without overstating the threat​

The advisory assigns a CVSS base score of 7.4 and a temporal score of 6.7. Its base assessment combines network access, high attack complexity, no required privileges, and no required user interaction. Confidentiality and integrity impacts are rated high; availability impact is rated none, with unchanged scope.

Those labels need to be read together:

  • Network access does not mean any remote attacker can exploit an arbitrary server immediately.
  • High complexity reflects the required position in the communication path.
  • No privileges required means the attacker does not first need an authorized account.
  • No user interaction means exploitation does not depend on someone clicking through a prompt.
  • No availability impact is not reassurance about confidentiality: a service can continue operating while information is exposed.

Microsoft’s original-publication assessment reported no known exploitation and no prior public disclosure, and characterized exploitation as less likely. Those statements describe the assessment at publication; they should not be rewritten as a permanent guarantee that exploitation cannot occur.

The temporal metrics also identify proof-of-concept exploit maturity. That does not establish that a working exploit was publicly released or deployed against customers. The maturity category, disclosure status, and observed-exploitation status answer different questions. Nor does the lower temporal score mean an individual installation has become safer without remediation.

For prioritization, the sensible reading is a consequential data-protection flaw with a meaningful exploitation prerequisite, rather than either an effortless Internet-wide compromise or a vulnerability that can safely be ignored.

Affected SqlClient versions and the fixed boundaries​

Microsoft’s published CVE record identifies three Microsoft.Data.SqlClient product lines and marks versions below the following boundaries as affected. Its product entries specify x64-based systems.

Microsoft.Data.SqlClient lineAffected versions within that lineFixed boundary
6.1Earlier than 6.1.76.1.7
7.0Earlier than 7.0.37.0.3
7.1Earlier than 7.1.0-preview37.1.0-preview3

These are package-version boundaries, not SQL Server engine build numbers. They also should not be stretched into unsupported conclusions about unlisted release lines or architectures.

A further distinction matters when choosing an update: the first fixed version is not necessarily the newest available version. Microsoft’s SqlClient release history now includes later stable releases, including 6.1.8, 7.0.4, and 7.1.2. The presence of a preview version in the CVE table is therefore not an instruction for every production application to migrate to preview software.

The release history also places 6.1.7 on September 10 and 7.1.0-preview3 on August 27, before the November advisory. This establishes that the vulnerability’s publication date and the availability date of a corrected package are not interchangeable; it does not establish why disclosure followed those releases.

The recommended deployment decision is to select an appropriate supported release that meets or exceeds the applicable fixed boundary, then validate compatibility. Do not downgrade an already newer installation merely to make its version match the advisory table.

A practical application-owner response​

The following is a recommended operational workflow, rather than a claim that Microsoft prescribes a particular organization’s deployment process.

1. Establish ownership and exposure​

Start with applications that use Microsoft.Data.SqlClient and connect to databases using Always Encrypted with secure enclaves. Assign an application owner and a database owner to each investigation.

Record the deployed package version, application release, target database, and whether enclave-backed operations are enabled. Separate confirmed facts from unanswered questions. “We use SQL Server” is not a sufficiently precise exposure assessment; neither is “the database is encrypted.”

For third-party software, request the vendor’s affected-version assessment and corrected application release. Avoid substituting individual libraries inside vendor-managed installations without an approved update procedure.

2. Inspect direct and transitive dependencies​

Microsoft’s.NET CLI documentation provides an inventory command that includes dependencies brought in by other packages. From the relevant project directory, with the appropriate SDK and package-feed access available, use the syntax matching your SDK.

For.NET 10 and later:

dotnet package list --include-transitive

For.NET 9 and earlier:

Code:
dotnet restore
dotnet list package --include-transitive

Microsoft documents that.NET 10 automatically restores when necessary; earlier versions require a restore or build first. Look for Microsoft.Data.SqlClient and inspect the Resolved version, rather than relying only on the requested version constraint. The transitive option includes dependencies that may not appear as direct references in the project.

Treat this as a source-project inventory step, not proof of what every production process is running. The recommended follow-up is to reconcile its results with deployment records and application artifacts.

3. Update through the application’s normal dependency process​

Choose a corrected package for the appropriate release line. Where another package controls the dependency, investigate that dependency relationship rather than assuming a single version edit completes the job.

Microsoft’s release notes contain package-alignment requirements for some newer releases. For example, its 7.1.2 release instructs users to keep the driver and companion packages on matching versions, while Microsoft.SqlServer.Server remains independently versioned. Review those compatibility requirements before deployment.

4. Validate the relevant application behavior​

A useful acceptance test should exercise the application’s actual encrypted-data operations, not merely confirm that a database connection opens. Recommended checks include representative reads, writes, and enclave-dependent queries, alongside the application’s normal authentication and error-handling tests.

Define success before rollout: the intended package is included in the deployed application, the required workflows still succeed, and the change is traceable to the affected deployment.

5. Close the deployment gap​

Recommend recording the corrected package version for each production application instance and retaining the validation results. A successful development build is an intermediate milestone; the operational objective is that the deployed applications no longer use the affected dependency.

If a discrepancy remains between project inventory and production evidence, keep the remediation task open until it is explained.

Where SQL Server security updates fit​

Microsoft’s advisory FAQ separately tells SQL Server administrators to install the applicable November 2026 security update and select the package matching their installed version and servicing branch. It distinguishes General Distribution Release updates, which deliver security and broadly applicable critical fixes, from cumulative updates containing accumulated fixes.

There is a trap here: a relevant monthly update is not automatically the direct fix for every CVE mentioned during that month.

For example, Microsoft Support documents KB5132748, released November 10, 2026, as the SQL Server 2025 GDR security update taking the engine to 17.0.1155.3. Its applicability covers SQL Server 2025 on Windows and Linux. However, the advisory list on that KB page does not name CVE-2026-62903. It therefore should not be presented as proof that this SqlClient vulnerability is remediated.

The recommended administrator workflow is consequently two-part:

  1. Identify the installed SQL Server engine version and servicing branch, then apply the appropriate engine security maintenance.
  2. Separately establish that affected applications have received the corrected Microsoft.Data.SqlClient dependency.

The advisory directs administrators to Microsoft’s KB321185 version guidance for selecting updates. It also explicitly cautions that omission from a version-selection table does not, by itself, establish that a release is unsupported; prerequisites and lifecycle status still require review.

For the example GDR package, Microsoft lists Windows Update, Microsoft Update Catalog, and Microsoft Download Center as acquisition methods, and specifies SQL Server 2025 or an applicable SQL Server 2025 GDR installation as a prerequisite. That information describes the engine package—not a delivery mechanism for updating every application’s NuGet dependency.

Hardening, caveats, and the bottom line​

Microsoft’s SQL Server security-update documentation recommends encryption with Extended Protection to help secure SQL Server on Windows. That is relevant general hardening guidance, but the documentation does not establish Extended Protection alone as a workaround for CVE-2026-62903.

Similarly, the advisory does not provide a verified interim procedure requiring administrators to disable Always Encrypted, bypass enclave validation, or rotate every encryption key. Such actions should not be improvised as substitutes for the documented correction. The public advisory describes potential key exposure; it does not establish that any particular customer’s keys were stolen.

The practical conclusion is straightforward: coordinate database maintenance with application dependency remediation. Prioritize investigation of secure-enclave workloads, match deployed SqlClient versions to the corrected boundaries, and retain evidence that the updated application—not just its source project—reached production.

CVE-2026-62903 is a reminder that database encryption is an end-to-end system. The server may hold the data, but the client participates in protecting the keys. A complete response needs both owners at the table.

 

References

  1. https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-62903/ msrc.microsoft.com
  2. CVE-2026-62903 — Microsoft.Data.SqlClient Information Disclosure Vulnerability · OpenAdvisories openadvisories.org
  3. KB5132748 - Description of the security update for SQL Server 2025 GDR: November 10, 2026 - SQL Server | Microsoft Support support.microsoft.com