Heap-based overflow in Microsoft SQL Server enables network-based privilege escalation on a widely deployed enterprise DB platform; high-impact for many organizations.
CVE-2026-68883
Heap overflow in Microsoft SQL Server enables network privilege escalation.
Is CVE-2026-68883 being exploited?
Not confirmed. CVE-2026-68883 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.39% probability of exploitation in the next 30 days.
How severe is CVE-2026-68883?
CVE-2026-68883 is rated High with a CVSS score of 8.5. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-68883?
Yes. A fix has been recorded for CVE-2026-68883. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-68883 affect?
CVE-2026-68883 affects Microsoft SQL Server (unspecified versions), Windows hosts running SQL Server. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-68883?
Apply Microsoft security update immediately; restrict SQL Server network access until patched.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Authenticated remote attacker can trigger a heap buffer overflow to elevate privileges (SQL Server service/sa or SYSTEM) over the network.
Immediate action required
- affected>= 14.0.3006.16 and < 14.0.3560.2
- affected>= 14.0.0 and < 14.0.2140.2
- affected>= 15.0.4003.23 and < 15.0.4500.2
- affected>= 15.0.0 and < 15.0.2200.2
- affected>= 16.0.4003.1 and < 16.0.4305.5
- affected>= 16.0.0 and < 16.0.1210.3
- affected>= 17.0.4006.2 and < 17.0.5015.4
- affected>= 17.0.1050.2 and < 17.0.1145.4
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.