Skip to main content
Mallory
HighVulnerability

CVE-2026-116934: Untrusted Pointer Dereference Privilege Escalation in Microsoft SQL Server

Published Nov 10, 2026 · Updated 4 days ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 days33 mentions · peak 30 in a dayToday
CVSS8.8High · v3.1
EPSS0.80%57th percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
Vendor
Microsoft Corporation
IdentifiersCVE-2026-116934CWE-822 · Untrusted Pointer Dereference

CVE-2026-116934 is an untrusted pointer dereference vulnerability in Microsoft SQL Server affecting releases 2017, 2019, 2022, and 2025. An authenticated attacker with permission to execute the affected database operation can submit a specially crafted network request to elevate privileges in the SQL Server service context. No user interaction is required. The affected function and exact triggering operation are not publicly specified. Microsoft rates the vulnerability Important and assigns a CVSS v3.1 base score of 8.8.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation allows an authenticated attacker to gain elevated privileges in the SQL Server service context, with potentially high confidentiality, integrity, and availability impacts. The exact resulting privilege level and whether privileges extend beyond the SQL Server service context are not specified.

Mitigation

If you can’t patch tonight, do this now.

No vulnerability-specific workaround is specified. Apply the applicable security update.

Remediation

Patch, then assume compromise.

Apply the November 10, 2026 security update matching the installed SQL Server release and servicing branch. Fixed CU+GDR builds are: SQL Server 2017, KB5132746, version 14.0.3570.2; SQL Server 2019, KB5132745, version 15.0.4510.2; SQL Server 2022, KB5129300, version 16.0.4315.2; and SQL Server 2025, KB5129299, version 17.0.5045.3. Fixed RTM/GDR builds are: SQL Server 2017, KB5132749, version 14.0.2150.2; SQL Server 2019, KB5132751, version 15.0.2210.4; SQL Server 2022, KB5132747, version 16.0.1220.3; and SQL Server 2025, KB5132748, version 17.0.1155.3. Verify update prerequisites and branch applicability before installation, or install a later applicable release containing the fix.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
Microsoft CorporationMicrosoft Sql Server 2017 For X64-Based Systems (Cu31)application
Microsoft CorporationMicrosoft Sql Server 2019 For X64-Based Systems (Cu32)application
Microsoft CorporationMicrosoft Sql Server 2022 For X64-Based Systems (Cu27)application
Microsoft CorporationSql Server 2019application
Microsoft CorporationSql Server 2022application
Microsoft CorporationSql Server 2025application
Microsoft CorporationSql Server 2025 For X64-Based Systems Cu10application
FAQ

Frequently asked questions

Is CVE-2026-116934 exploited in the wild?
As of Nov 14, 2026, Mallory has no reports of CVE-2026-116934 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-116934?
As of Nov 14, 2026, Mallory has found no public exploit for CVE-2026-116934.
Is there a patch for CVE-2026-116934?
Apply the November 10, 2026 security update matching the installed SQL Server release and servicing branch. Fixed CU+GDR builds are: SQL Server 2017, KB5132746, version 14.0.3570.2; SQL Server 2019, KB5132745, version 15.0.4510.2; SQL Server 2022, KB5129300, version 16.0.4315.2; and SQL Server 2025, KB5129299, version 17.0.5045.3.
What products are affected by CVE-2026-116934?
Microsoft Corporation Microsoft Sql Server 2017 For X64-Based Systems (Cu31), Microsoft Corporation Microsoft Sql Server 2019 For X64-Based Systems (Cu32), Microsoft Corporation Microsoft Sql Server 2022 For X64-Based Systems (Cu27), Microsoft Corporation Sql Server 2019, Microsoft Corporation Sql Server 2022, and 2 more.
How severe is CVE-2026-116934?
CVE-2026-116934 has a CVSS v3.1 score of 8.8 (High) and an EPSS score of 0.80% (57th percentile) as of Nov 14, 2026.
Activity feed

Recent activity

33 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
tenable nessus pluginsNews · Nov 13, 2026Security Updates for Microsoft SQL Server (November 2026) | Tenable®A Microsoft SQL Server vulnerability covered by the security updates. The content does not describe its specific mechanism or impact.Read more ↗tenable nessus pluginsNews · Nov 13, 2026Security Updates for Microsoft SQL Server (November 2026) | Tenable®A Microsoft SQL Server vulnerability covered by the security update. Its specific mechanism and impact are not described.Read more ↗ghsa syntheticNews · Nov 10, 2026GHSA-rwhq-2m3q-7ccgAn untrusted pointer dereference vulnerability in SQL Server that allows an authorized attacker to elevate privileges over a network.Read more ↗zeropath blogNews · Nov 10, 2026Brief Summary: CVE-2026-116934 in Microsoft SQL Server, an Untrusted Pointer Dereference Enabling Privilege Escalation - ZeroPath Blog | ZeroPathA high-severity untrusted pointer dereference vulnerability affecting Microsoft SQL Server 2017, 2019, 2022 and 2025. Exploitation requires authenticated access and permission to execute an unspecified database operation; no user interaction is required. Microsoft assigns CVSS 3.1 severity 8.8 and rates exploitation less likely. The confirmed impact is privilege escalation within the SQL Server service context, not necessarily Windows SYSTEM access. Official fixes were released November 10, 2026, across GDR and CU servicing branches. Some updates introduce a documented database-recovery regression involving sys.dm_exec_requests; its workarounds do not mitigate this vulnerability.Read more ↗
+27 more in the timeline. Sign up to see them
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activityCommunity discussion across Reddit, Mastodon, and other social sources.