Microsoft SQL Server Remote Code Execution Vulnerability

Check whether my systems are affected by CVE-2026-116936 (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-116936 (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-116936 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-116936 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-116936
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.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-116936
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-116936.