CVE-2026-94512
Heap-based buffer overflow in SQL Server allows an authorized attacker to execute code over a network.
Executive briefing
The source record describes: Heap-based buffer overflow in SQL Server allows an authorized attacker to execute code over a network. The practical risk depends on whether an affected product/version is present, reachable and configured in an exploitable way. Review the affected-product evidence and linked vendor advisories before assigning exposure status.
Evidence confidence: Moderate Evidence-derived, not an exploitability verdict
Severity & attack characteristics
CVSS vector:CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Technical explanation & impact
The technical mechanism is not expanded beyond the source description unless a referenced advisory supplies additional evidence. Read the linked vendor/CERT advisories for root-cause detail.
Potential impact must be interpreted from the published CVSS impact metrics and the affected component. A CVSS impact score is not proof that a particular asset is exploitable.
Weakness classification
CWE-122Affected products and versions
Products below are parsed from NVD vulnerable CPE configuration entries. Version boundaries are shown as published; verify applicability with the vendor.
| Vendor | Product | Version evidence |
|---|---|---|
| microsoft | sql_server_2017 | from (inclusive) 14.0.3006.16; before 14.0.3560.2 |
| microsoft | sql_server_2019 | from (inclusive) 15.0.4003.23; before 15.0.4500.2 |
| microsoft | sql_server_2022 | from (inclusive) 16.0.4003.1; before 16.0.4305.5 |
| microsoft | sql_server_2025 | from (inclusive) 17.0.4006.2; before 17.0.5015.4 |
Remediation & validation
- Identify exposure by comparing the affected product and version ranges with your asset inventory, SBOM and externally exposed services.
- Review the linked vendor security advisory or patch notes. Upgrade to a vendor-confirmed fixed release; do not infer a fixed version from the CVE description.
- Until patched, consider restricting network access or disabling the affected feature where operationally safe. These are temporary controls, not a substitute for a vendor fix.
- Validate the remediation with a version check and vulnerability rescan, then retain change evidence.
No fixed version is displayed unless it is explicitly established by a vendor advisory. Follow the vendor's release notes for exact product and branch applicability.
Vendor advisories, patches & exploit references
- https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-94512 PATCH secure@microsoft.com