Skip to main content
Mallory
MediumVulnerability

CVE-2026-118103: Microsoft SQL Server Out-of-Bounds Read Information Disclosure

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
CVSS6.5Medium · v3.1
EPSS0.86%59th percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
Vendor
Microsoft Corporation
IdentifiersCVE-2026-118103CWE-125 · Out-of-bounds Read

CVE-2026-118103 is an out-of-bounds read vulnerability in Microsoft SQL Server affecting SQL Server 2017, 2019, 2022, and 2025. An unauthenticated attacker can exploit it over a network, with user interaction required, to disclose heap memory from a privileged process running on the server. The specific vulnerable function and triggering input are not identified. Microsoft rates the vulnerability Important, with a CVSS v3.1 base score of 6.5.

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 can expose heap memory belonging to a privileged server process, potentially disclosing sensitive information. The CVSS assessment indicates high confidentiality impact and no integrity or availability impact. The specific information exposed and extent of the memory disclosure are not specified.

Mitigation

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

No vulnerability-specific workaround or temporary mitigation is specified. Apply the applicable SQL Server security update.

Remediation

Patch, then assume compromise.

Apply the November 10, 2026 security update appropriate to the installed SQL Server release and servicing branch: SQL Server 2017 CU31+GDR—KB5132746, build 14.0.3570.2; SQL Server 2017 RTM+GDR—KB5132749, build 14.0.2150.2; SQL Server 2019 CU32+GDR—KB5132745, build 15.0.4510.2; SQL Server 2019 RTM+GDR—KB5132751, build 15.0.2210.4; SQL Server 2022 CU27+GDR2—KB5129300, build 16.0.4315.2; SQL Server 2022 RTM+GDR—KB5132747, build 16.0.1220.3; SQL Server 2025 CU10+GDR—KB5129299, build 17.0.5045.3; SQL Server 2025 RTM+GDR—KB5132748, build 17.0.1155.3. Verify update prerequisites and applicability to the installed build 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-118103 exploited in the wild?
As of Nov 14, 2026, Mallory has no reports of CVE-2026-118103 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-118103?
As of Nov 14, 2026, Mallory has found no public exploit for CVE-2026-118103.
Is there a patch for CVE-2026-118103?
Apply the November 10, 2026 security update appropriate to the installed SQL Server release and servicing branch: SQL Server 2017 CU31+GDR—KB5132746, build 14.0.3570.2; SQL Server 2017 RTM+GDR—KB5132749, build 14.0.2150.2; SQL Server 2019 CU32+GDR—KB5132745, build 15.0.4510.2; SQL Server 2019 RTM+GDR—KB5132751, build 15.0.2210.4; SQL Server 2022 CU27+GDR2—KB5129300, build 16.0.4315.2; SQL Server 2022 RTM+GDR—KB5132747, build 16.0.1220.3; SQL Server 2025 CU10+GDR—KB5129299, build 17.0.5045.3; SQL Server 2025 RTM+GDR—KB5132748, build 17.0.1155.3. Verify update prerequisites and applicability to the installed build before deployment.
What products are affected by CVE-2026-118103?
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-118103?
CVE-2026-118103 has a CVSS v3.1 score of 6.5 (Medium) and an EPSS score of 0.86% (59th 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.