cve.bz

CVE-2026-62903 Microsoft.Data.SqlClient Information Disclosure Vulnerability

7.4 highEPSS 0.6%

High (7.4) in microsoft. EPSS 0.6% estimated probability of exploitation activity in the next 30 days.

On this page
Authentication bypass by capture-replay in SQL Server allows an unauthorized attacker to disclose information over a network.

Severity

CVSS 3.1

7.4 high
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N
EPSS
0.6% estimated probability of exploitation activity in the next 30 days; 52nd 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-11. 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-294 Authentication Bypass by Capture-replay
OWASP Top 10
A07:2025 Authentication Failures
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-62903 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-62903?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-62903?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-62903 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-62903

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-62903](https://cve.bz/cve/badge/CVE-2026-62903.svg)](https://cve.bz/cve/CVE-2026-62903)

HTML:

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

Affected

  • microsoft:microsoft.data.sqlclient 6.1
  • microsoft:microsoft.data.sqlclient 7.0
  • microsoft:microsoft.data.sqlclient 7.1

Versions

From the CNA's record in the CVE List.

ProductAffected
Microsoft.Data.SqlClient 6.1from 1.0.0.0 before 6.1.7
Microsoft.Data.SqlClient 7.0from 1.0.0.0 before 7.0.3
Microsoft.Data.SqlClient 7.1from 1.0.0.0 before 7.1.0-preview3

Attack patterns (CAPEC)

  • CAPEC-60 Reusing Session IDs (aka Session Replay) Likelihood: High · Severity: High
  • CAPEC-94 Adversary in the Middle (AiTM) Likelihood: High · Severity: Very High
  • CAPEC-102 Session Sidejacking Likelihood: High · Severity: High
  • CAPEC-509 Kerberoasting Severity: High
  • CAPEC-555 Remote Services with Stolen Credentials Severity: Very High
  • CAPEC-561 Windows Admin Shares with Stolen Credentials
  • CAPEC-644 Use of Captured Hashes (Pass The Hash) Likelihood: Medium · Severity: High
  • CAPEC-645 Use of Captured Tickets (Pass The Ticket) Likelihood: Low · Severity: High
  • CAPEC-652 Use of Known Kerberos Credentials Likelihood: Medium · Severity: High
  • CAPEC-701 Browser in the Middle (BiTM) Likelihood: Medium · Severity: High

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

References

Check your stackJSON