cve.bz

CVE-2026-118103 Microsoft SQL Server Information Disclosure Vulnerability

6.5 mediumEPSS 0.9%

Medium (6.5) in microsoft. EPSS 0.9% estimated probability of exploitation activity in the next 30 days.

On this page
Out-of-bounds read in SQL Server allows an unauthorized attacker to disclose information over a network.

Severity

CVSS 3.1

6.5 medium
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N
EPSS
0.9% estimated probability of exploitation activity in the next 30 days; 59th percentile. Scored 2026-11-13. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2026-11-10. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-125 Out-of-bounds Read
Published
Modified
Assigned by
microsoft (CNA)
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Ask an AI about this CVE

ChatGPTClaudeGoogle AI Mode

Show the promptExplain CVE-2026-118103 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-118103?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-118103?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-118103 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Badge for a README or a site

CVE-2026-118103

An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:

[![CVE-2026-118103](https://cve.bz/cve/badge/CVE-2026-118103.svg)](https://cve.bz/cve/CVE-2026-118103)

HTML:

<a href="https://cve.bz/cve/CVE-2026-118103"><img src="https://cve.bz/cve/badge/CVE-2026-118103.svg" alt="CVE-2026-118103"></a>

Affected

  • microsoft:microsoft sql server 2017 (gdr)
  • microsoft:microsoft sql server 2017 for x64-based systems (cu31)
  • microsoft:microsoft sql server 2019 (gdr)
  • microsoft:microsoft sql server 2019 for x64-based systems (cu32)
  • microsoft:microsoft sql server 2022 (gdr)
  • microsoft:microsoft sql server 2022 for x64-based systems (cu27)
  • microsoft:microsoft sql server 2025 cu10
  • microsoft:microsoft sql server 2025 for x64-based systems (gdr)

Versions

From the CNA's record in the CVE List.

ProductAffected
Microsoft SQL Server 2017 (GDR)from 14.0.0 before 14.0.2150.2
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
Microsoft SQL Server 2025 CU10from 17.0.4006.0 before 17.0.5045.3
Microsoft SQL Server 2025 for x64-based Systems (GDR)from 17.0.1050.2 before 17.0.1155.3

Attack patterns (CAPEC)

  • CAPEC-540 Overread Buffers Likelihood: Low · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON