CVE-2026-67637: Microsoft SQL Server heap-based buffer overflow

CVE-2026-67637 · Severity: high · CVSS 8.8 · Published 2026-11-10

SQL Server, Microsoft's database management system used by organizations to store and manage critical business data, contains a heap-based buffer overflow vulnerability. An authenticated attacker with network access could exploit this flaw to execute arbitrary code on the server, potentially leading to data theft, corruption, or loss of availability of the database system.

Technologies: Microsoft SQL Server. Vendors: Microsoft.

Quick answers

Is CVE-2026-67637 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-67637 being exploited in the wild.
How severe is CVE-2026-67637?
High severity, with a CVSS score of 8.8, published 10 November 2026.
Which products and versions are affected?
Microsoft SQL Server.
Is there a fix for CVE-2026-67637?
No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
How is CVE-2026-67637 attacked?
It is attacked over the network.
Am I affected by CVE-2026-67637?
Check whether you run Microsoft SQL Server. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Technical details

A heap-based buffer overflow exists in SQL Server that can be triggered by an authenticated network attacker to achieve remote code execution. The vulnerability requires valid database credentials to exploit and allows an attacker to write arbitrary data to the heap, potentially overwriting function pointers or other critical memory structures to gain code execution.

Affected products

  • Microsoft SQL Server

Timeline

  • 2026-11-10: disclosed

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.