Skip to content
Tuesday, October 13, 2026AboutContactRSS
Vulnerabilities

High-Severity Heap-Based Buffer Overflow Flaw in Microsoft SQL Server 2017 (GDR) Tracked as CVE-2026-68883

A newly published high vulnerability in Microsoft SQL Server 2017 (GDR) carries a CVSS score of 8.5. Here is what is affected and how to respond.

Illustration: A sleek black server tower sits in a dimly lit room with its side panel removed.
AI-generated illustration: Threat Times

Key points

  • CVE-2026-68883 affects Microsoft SQL Server 2017 (GDR).
  • CVSS 8.5 (High).
  • No exploitation confirmed yet.

A high heap-based buffer overflow tracked as CVE-2026-68883 has been published in the National Vulnerability Database for Microsoft SQL Server 2017 (GDR), with a CVSS base score of 8.5.

At a glance

CVE
CVE-2026-68883
Product
Microsoft SQL Server 2017 (GDR)
CVSS
8.5 High
Weakness
heap-based buffer overflow
Exploited
No known exploitation

What is the vulnerability?

The NVD entry states: Heap-based buffer overflow in SQL Server allows an authorized attacker to elevate privileges over a network.

Affected versions

VendorProductVersions
MicrosoftMicrosoft SQL Server 2017 (GDR)before 14.0.2140.2
MicrosoftMicrosoft SQL Server 2017 for x64-based Systems (CU31)before 14.0.3560.2
MicrosoftMicrosoft SQL Server 2019 (GDR)before 15.0.2200.2
MicrosoftMicrosoft SQL Server 2019 for x64-based Systems (CU32)before 15.0.4500.2
MicrosoftMicrosoft SQL Server 2022 (GDR)before 16.0.1210.3
MicrosoftMicrosoft SQL Server 2022 for x64-based Systems (CU27)before 16.0.4305.5
MicrosoftMicrosoft SQL Server 2025 (CU8)-
MicrosoftMicrosoft SQL Server 2025 for x64-based Systems (CU9)before 17.0.5015.4

CVSS vector: CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H/E:U/RL:O/RC:C.

Is it being exploited?

There is no public confirmation of exploitation at the time of publication. It does not appear in CISA's Known Exploited Vulnerabilities catalog. We will update this report if that changes.

What should you do?

  • Identify whether the affected product and versions run in your environment.
  • Apply the vendor update listed in the advisory as soon as it is available.
  • Limit network exposure of the affected service until it is patched.
  • Monitor the vendor advisory for updated guidance or exploitation reports.

What to do and how to stay safe: CVE-2026-68883

  • Vulnerability severity scores ignore your specific architecture and context.
  • Exploitability depends on network exposure and user behavior, not just code flaws.
  • Prioritization requires continuous asset inventory and threat intelligence alignment.

Risk-based vulnerability management focuses your limited resources on the flaws that actually threaten your business. Start by mapping your critical assets and checking for active exploits to prioritize your backlog.

Step-by-step guide: Risk-Based Vulnerability Management: Prioritize Fixes by Actual Danger

General security guidance from the Threat Times newsroom. It is not confirmed advice from the organisations named in this story.

Frequently asked questions

What is CVE-2026-68883?

CVE-2026-68883 is a heap-based buffer overflow vulnerability in Microsoft SQL Server 2017 (GDR).

How severe is CVE-2026-68883?

It has a CVSS score of 8.5 High.

Is CVE-2026-68883 being exploited?

There is no public confirmation of exploitation at the time of publication.

Sources

  1. NVD — CVE-2026-68883
  2. Reference
CVE-2026-68883Microsoft SQL Server 2017 (GDR)High severity
Related articles