Skip to content
Fencer Vulns
high 7.7

CVE-2026-85888 json

Microsoft SQL Server Information Disclosure Vulnerability

published 2026-10-13 26 d ago modified 2026-10-31 8 d ago also EUVD-2026-100612

cvss
7.7
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.8%
EPSS 0.8% chance of exploitation in 30 days, percentile 56%
public exploits
0
none known

Summary

Out-of-bounds read in SQL Server allows an authorized attacker to disclose information over a network.

Patch / fix

  • Microsoft Microsoft SQL Server 2017 (GDR) 14.0.2140.2
  • Microsoft Microsoft SQL Server 2017 for x64-based Systems (CU31) 14.0.3560.2
  • Microsoft Microsoft SQL Server 2019 (GDR) 15.0.2200.2
  • Microsoft Microsoft SQL Server 2019 for x64-based Systems (CU32) 15.0.4500.2
  • Microsoft Microsoft SQL Server 2022 (GDR) 16.0.1210.3
  • Microsoft Microsoft SQL Server 2022 for x64-based Systems (CU27) 16.0.4305.5
  • Microsoft Microsoft SQL Server 2025 for x64-based Systems (CU9) 17.0.5015.4
  • Microsoft Microsoft SQL Server 2025 for x64-based Systems (GDR) 17.0.1145.4

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
partial
Assessed
26 d ago

Exploit prediction

0.80% chance of exploitation in the next 30 days, higher than 56% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
CNA 3.1 7.7 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N/E:U/RL:O/RC:C
CNA 3.1 7.7 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N

Affected products

  • 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 for x64-based Systems (CU9)
  • Microsoft Microsoft SQL Server 2025 for x64-based Systems (GDR)

Classification

Weakness
Technology feeds

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.