CVE-2026-67373

8.8

Microsoft · SQL Server 2025

A heap-based buffer overflow in Microsoft SQL Server 2025 allows an authenticated attacker to achieve remote code execution.

Executive summary

A heap-based buffer overflow in Microsoft SQL Server 2025 creates a high-risk scenario where an authenticated attacker can execute arbitrary code on the database server.

Vulnerability

This is a heap-based buffer overflow (CWE-122) vulnerability occurring within the SQL Server engine. The vulnerability requires the attacker to have low-level privileges (authenticated) to trigger the overflow, which can result in remote code execution over the network.

Business impact

The potential for remote code execution represents a critical threat to data integrity, confidentiality, and system availability. With a CVSS score of 8.8, this vulnerability is classified as High severity, as successful exploitation allows an attacker to gain full control over the database instance, potentially leading to unauthorized data exfiltration or total system compromise.

Remediation

Immediate Action: Update Microsoft SQL Server 2025 instances to version 17.0.4085.5 or 17.0.1135.8, depending on the specific edition in use, as specified in the Microsoft security update guide.

Proactive Monitoring: Review database audit logs for unusual stored procedure execution or abnormal service behavior that may indicate an attempt to exploit memory-based vulnerabilities.

Compensating Controls: Ensure that database access is strictly limited to authorized users and implement network segmentation to prevent lateral movement to the database server from untrusted network segments.

Exploitation status

Public Exploit Available: No

Analyst recommendation

Given the potential for remote code execution, organizations should prioritize testing and deploying the provided security updates across all affected SQL Server environments. Patching is the only effective way to remediate this memory safety flaw, and administrators should ensure compliance with their internal update cycles to mitigate the risk of exploitation.

More Microsoft CVEs all →

History

  1. Disclosed CVE record published
  2. Collected by CVE Brief via github
  3. Analyst report written
  4. Published in the daily brief high section

Sources