Skip to main content
Mallory
HighVulnerability

CVE-2026-118112: Code Injection Leading to 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 days32 mentions · peak 29 in a dayToday
CVSS8.0High · v3.1
EPSS0.92%61st percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
Vendor
Microsoft Corporation
IdentifiersCVE-2026-118112CWE-94 · Improper Control of Generation of…

CVE-2026-118112 is a code-injection vulnerability in Microsoft SQL Server 2017, 2019, 2022, and 2025. Improper control of code generation allows an authenticated attacker with permission to create or modify database objects to prepare malicious database content. When a separate administrator performs an affected administrative operation on that content, attacker-controlled database commands can execute with elevated privileges. The specific vulnerable function and administrative operation are not identified. Microsoft rates the vulnerability Important, with a CVSS v3.1 base score of 8.0.

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 permits privilege escalation through execution of database commands with elevated privileges and can have high confidentiality, integrity, and availability impacts. Operating-system-level code execution is not established.

Mitigation

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

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

Remediation

Patch, then assume compromise.

Install the applicable November 2026 security update for the installed SQL Server version and servicing branch: SQL Server 2017 CU—KB5132746 (14.0.3570.2), or RTM/GDR—KB5132749 (14.0.2150.2); SQL Server 2019 CU—KB5132745 (15.0.4510.2), or RTM/GDR—KB5132751 (15.0.2210.4); SQL Server 2022 CU—KB5129300 (16.0.4315.2), or RTM/GDR—KB5132747 (16.0.1220.3); SQL Server 2025 CU—KB5129299 (17.0.5045.3), or RTM/GDR—KB5132748 (17.0.1155.3). A later applicable release containing the fix may also be used. Confirm the installed servicing branch and update prerequisites before deployment.

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 2017application
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-118112 exploited in the wild?
As of Nov 14, 2026, Mallory has no reports of CVE-2026-118112 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-118112?
As of Nov 14, 2026, Mallory has found no public exploit for CVE-2026-118112.
Is there a patch for CVE-2026-118112?
Install the applicable November 2026 security update for the installed SQL Server version and servicing branch: SQL Server 2017 CU—KB5132746 (14.0.3570.2), or RTM/GDR—KB5132749 (14.0.2150.2); SQL Server 2019 CU—KB5132745 (15.0.4510.2), or RTM/GDR—KB5132751 (15.0.2210.4); SQL Server 2022 CU—KB5129300 (16.0.4315.2), or RTM/GDR—KB5132747 (16.0.1220.3); SQL Server 2025 CU—KB5129299 (17.0.5045.3), or RTM/GDR—KB5132748 (17.0.1155.3). A later applicable release containing the fix may also be used.
What products are affected by CVE-2026-118112?
Microsoft Corporation Sql Server 2017, 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, and 3 more.
How severe is CVE-2026-118112?
CVE-2026-118112 has a CVSS v3.1 score of 8.0 (High) and an EPSS score of 0.92% (61st percentile) as of Nov 14, 2026.
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.