Skip to main content
Menu
CVEs

Microsoft SQL Server privilege escalation via untrusted pointer dereference

CVE-2026-116934EUVD-2026-122526GHSA-RWHQ-2M3Q-7CCGPublished November 10, 2026, updated

8.8HighCNA
Exploited
No known exploitation
Fix
Fixed in 2017 CU31 14.0.3570.2, 2019 GDR 15.0.2210.4, 2019 CU32 15.0.4510.2, 2022 GDR 16.0.1220.3, 2022 CU27 16.0.4315.2, 2025 CU10 17.0.5045.3, 2025 GDR 17.0.1155.3
Who is exposed
Not reported

Summary

Microsoft SQL Server contains an elevation of privilege flaw caused by an untrusted pointer dereference. An attacker with low-privilege login can exploit it remotely over the network, without any user action, to gain higher privileges on the system.

Written by a model

Original description

Untrusted pointer dereference in SQL Server allows an authorized attacker to elevate privileges over a network.

What to do

Upgrade to a fixed version: 2017 CU31 14.0.3570.2, 2019 GDR 15.0.2210.4, 2019 CU32 15.0.4510.2, 2022 GDR 16.0.1220.3, 2022 CU27 16.0.4315.2, 2025 CU10 17.0.5045.3, 2025 GDR 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-116934 (Microsoft SQL Server Elevation of Privilege 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-116934 (entry last updated 2026-11-19):
Affected:
- 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.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-116934 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-116934 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-116934
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-116934
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-116934"}.

Affected versions

cve.now Index

30of 100 · methodology v3
  • 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

Timeline

  1. CVE published
  2. First seen by cve.now
  3. Posted on X by cve.now
  4. CISA SSVC assessment

    Exploitation: none · Automatable: no · Technical impact: total

    9 days
  5. Record last updated

Public exploit activity

100%0Posted on X by cve.nowNov 10Nov 22
  • EPSS: 0.80%
  • Posted on X by cve.now Nov 10

Since disclosure: the repos PoC-in-GitHub lists and FIRST's daily EPSS score.

Evidence 3

KindSource
Vendor advisory 1Establishes: Affected and fixed versions.
Patchmsrc.microsoft.com · update-guide/vulnerability/CVE-2026-116934
CVE record 2Establishes: The identifier and description.
RecordCVE List · CVE-2026-116934
RecordNVD · CVE-2026-116934

Questions about CVE-2026-116934

Is CVE-2026-116934 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-116934?

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. Microsoft SQL Server 2022 for x64-based Systems (CU27): from 16.0.4003.1 before 16.0.4315.2. 2 more packages are listed on the page.

Source: cve.now feed data

How do I fix CVE-2026-116934?

Upgrade to a fixed version: 2017 CU31 14.0.3570.2, 2019 GDR 15.0.2210.4, 2019 CU32 15.0.4510.2, 2022 GDR 16.0.1220.3, 2022 CU27 16.0.4315.2, 2025 CU10 17.0.5045.3, 2025 GDR 17.0.1155.3.

Source: cve.now feed data

No corrections so far. Something wrong on this page? Report an error.