CVE-2026-116941: Microsoft SQL Server (high)

Summary

Microsoft SQL Server is affected by a heap-based buffer overflow that lets an attacker run code on the server. The attack can be carried out remotely over the network by someone who has a low-privilege login, and no user action is needed.

Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.

Read the original description

Heap-based buffer overflow in SQL Server allows an authorized attacker to execute code over a network.

cve.now Index

30Pcve.now Index 30 of 100 · methodology v3 · provisional

Exploitation0/40No signal
Exposure3/25Reachable over the network · Unknown: No advisory context yet
Reach17/20Affects Microsoft SQL Server (a widely deployed server, runtime, framework or database)
Severity9.8/10CVSS 8.8, total technical impact per CISA
No patch0/5No signal

What would change the score

Would score about 85 if added to CISA KEV
Would score about 80 if CISA's SSVC rates exploitation active
Would score about 49 if advisories confirm default setups are exposed

How the score works · Rankings

What to do

Upgrade to a fixed version: Microsoft SQL Server 14.0.2150.2, 15.0.2210.4, 16.0.1220.3 · Microsoft SQL Server 2017 for x64-based Systems 14.0.3570.2 · Microsoft SQL Server 2019 for x64-based Systems 15.0.4510.2 · Microsoft SQL Server 2022 for x64-based Systems 16.0.4315.2 · Microsoft SQL Server 2025 CU10 17.0.5045.3 · Microsoft SQL Server 2025 for x64-based Systems 17.0.1155.3.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-116941 (Microsoft SQL Server Remote Code Execution Vulnerability), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-116941 (entry last updated 2026-11-10):
Affected:
- Microsoft Microsoft SQL Server 2017 (GDR): from 14.0.0, fixed in 14.0.2150.2
- Microsoft Microsoft SQL Server 2017 for x64-based Systems (CU31): from 14.0.3006.16, fixed in 14.0.3570.2
- Microsoft Microsoft SQL Server 2019 (GDR): from 15.0.0, fixed in 15.0.2210.4
- Microsoft Microsoft SQL Server 2019 for x64-based Systems (CU32): from 15.0.4003.23, fixed in 15.0.4510.2
- Microsoft Microsoft SQL Server 2022 (GDR): from 16.0.0, fixed in 16.0.1220.3
- Microsoft Microsoft SQL Server 2022 for x64-based Systems (CU27): from 16.0.4003.1, fixed in 16.0.4315.2
- Microsoft Microsoft SQL Server 2025 CU10: from 17.0.4006.0, fixed in 17.0.5045.3
- Microsoft Microsoft SQL Server 2025 for x64-based Systems (GDR): from 17.0.1050.2, fixed in 17.0.1155.3
Fixed versions: 14.0.2150.2, 14.0.3570.2, 15.0.2210.4, 15.0.4510.2, 16.0.1220.3, 16.0.4315.2, 17.0.5045.3, 17.0.1155.3.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-116941 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-116941 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-116941
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Entry: https://cve.now/CVE-2026-116941
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example get_vulnerability with id CVE-2026-116941.

Timeline

Nov 10, 2026, 6:24 PM UTCCVE published
Nov 10, 2026, 6:34 PM UTCFirst seen by cve.now
Nov 10, 2026, 7:19 PM UTCPosted on X by cve.now
Nov 10, 2026, 7:53 PM UTCCISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
Nov 10, 2026, 7:59 PM UTCRecord last updated

Affected versions

Microsoft Microsoft SQL Server 2017 (GDR)
From 14.0.0 · fixed in 14.0.2150.2
Microsoft Microsoft SQL Server 2017 for x64-based Systems (CU31)
From 14.0.3006.16 · fixed in 14.0.3570.2
Microsoft Microsoft SQL Server 2019 (GDR)
From 15.0.0 · fixed in 15.0.2210.4
Microsoft Microsoft SQL Server 2019 for x64-based Systems (CU32)
From 15.0.4003.23 · fixed in 15.0.4510.2
Microsoft Microsoft SQL Server 2022 (GDR)
From 16.0.0 · fixed in 16.0.1220.3
Microsoft Microsoft SQL Server 2022 for x64-based Systems (CU27)
From 16.0.4003.1 · fixed in 16.0.4315.2
Microsoft Microsoft SQL Server 2025 CU10
From 17.0.4006.0 · fixed in 17.0.5045.3
Microsoft Microsoft SQL Server 2025 for x64-based Systems (GDR)
From 17.0.1050.2 · fixed in 17.0.1155.3

Evidence 3

Vendor advisory · 1

Establishes: Affected and fixed versions.

Patch
msrc.microsoft.com · update-guide/vulnerability/CVE-2026-116941

CVE record · 2

Establishes: The identifier and description.

Record
CVE List · CVE-2026-116941
Record
NVD · CVE-2026-116941

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

Questions about CVE-2026-116941

Is CVE-2026-116941 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data

Which versions are affected by CVE-2026-116941?

Microsoft SQL Server 2017 (GDR): from 14.0.0 before 14.0.2150.2. Microsoft SQL Server 2017 for x64-based Systems (CU31): from 14.0.3006.16 before 14.0.3570.2. Microsoft SQL Server 2019 (GDR): from 15.0.0 before 15.0.2210.4. Microsoft SQL Server 2019 for x64-based Systems (CU32): from 15.0.4003.23 before 15.0.4510.2. Microsoft SQL Server 2022 (GDR): from 16.0.0 before 16.0.1220.3. 3 more packages are listed on the page.Source: cve.now feed data

How do I fix CVE-2026-116941?

Upgrade to a fixed version: Microsoft SQL Server 14.0.2150.2, 15.0.2210.4, 16.0.1220.3 · Microsoft SQL Server 2017 for x64-based Systems 14.0.3570.2 · Microsoft SQL Server 2019 for x64-based Systems 15.0.4510.2 · Microsoft SQL Server 2022 for x64-based Systems 16.0.4315.2 · Microsoft SQL Server 2025 CU10 17.0.5045.3 · Microsoft SQL Server 2025 for x64-based Systems 17.0.1155.3.Source: cve.now feed data

Microsoft SQL Server Remote Code Execution Vulnerability