CVE-2026-88081: Microsoft SQL Server Information Disclosure Vulnerability
Noroxi assessment
Priority: Monitor (action score 30/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.79% (FIRST EPSS); higher than 56.9% of all records.
- Anyone who can reach it over the internet can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Microsoft SQL Server 2017 for x64-based Systems (CU31) 14.0.3560.2; Microsoft SQL Server 2017 for x64-based Systems (GDR) 14.0.2140.2; Microsoft SQL Server 2019 for x64-based Systems (CU32) 15.0.4500.2.
Low priority for now. Upgrade to Microsoft SQL Server 2017 for x64-based Systems (CU31) 14.0.3560.2; Microsoft SQL Server 2017 for x64-based Systems (GDR) 14.0.2140.2; Microsoft SQL Server 2019 for x64-based Systems (CU32) 15.0.4500.2 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
Out-of-bounds read in SQL Server allows an authorized attacker to disclose information over a network.
- Published
- Oct 13, 2026
- Updated
- Nov 10, 2026
- EPSS
- 0.7% · 56th percentile
- CWE
- CWE-125
Report tools
Action score
30
Low priority for now.
- CVSS
- 30 / 40 · 7.7 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.7%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · microsoft
- 7.7
- NVD has not scored this yet; the score shown is the CNA’s.
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
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (microsoft). Independent of NVD's CPE analysis and usually ahead of it.
Microsoft Microsoft SQL Server 2017 (GDR)
- 14.0.0 and later · before 14.0.2140.2affected
Microsoft Microsoft SQL Server 2017 for x64-based Systems (CU31)
- 14.0.3006.16 and later · before 14.0.3560.2affected
Microsoft Microsoft SQL Server 2019 (GDR)
- 15.0.0 and later · before 15.0.2200.2affected
Microsoft Microsoft SQL Server 2019 for x64-based Systems (CU32)
- 15.0.4003.23 and later · before 15.0.4500.2affected
Microsoft Microsoft SQL Server 2022 (GDR)
- 16.0.0 and later · before 16.0.1210.3affected
Microsoft Microsoft SQL Server 2022 for x64-based Systems (CU27)
- 16.0.4003.1 and later · before 16.0.4305.5affected
Microsoft Microsoft SQL Server 2025 for x64-based Systems (CU9)
- 17.0.4006.2 and later · before 17.0.5015.4affected
Microsoft Microsoft SQL Server 2025 for x64-based Systems (GDR)
- 17.0.1050.2 and later · before 17.0.1145.4affected
Same product
microsoft: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-116945Microsoft SQL Server Remote Code Execution Vulnerability39Monitor
- CVE-2026-94511SQL Server Remote Code Execution Vulnerability35Monitor
- CVE-2026-67637Microsoft SQL Server Remote Code Execution Vulnerability35Monitor
Published before and after this one in the same product
- ← EarlierCVE-2026-67628Oct 13, 2026 · Microsoft SQL Server Information Disclosure Vulnerability19Monitor
- ← EarlierCVE-2026-85888Oct 13, 2026 · Microsoft SQL Server Information Disclosure Vulnerability30Monitor
- Later →CVE-2026-94520Oct 13, 2026 · Microsoft SQL Server Denial of Service Vulnerability19Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Microsoft SQL Server 2017 for x64-based Systems (CU31) | 14.0.3560.2 · KB5128496 | Microsoft (MSRC) |
| Microsoft SQL Server 2017 for x64-based Systems (GDR) | 14.0.2140.2 · KB5128497 | Microsoft (MSRC) |
| Microsoft SQL Server 2019 for x64-based Systems (CU32) | 15.0.4500.2 · KB5128494 | Microsoft (MSRC) |
| Microsoft SQL Server 2019 for x64-based Systems (GDR) | 15.0.2200.2 · KB5128495 | Microsoft (MSRC) |
| Microsoft SQL Server 2022 for x64-based Systems (CU27) | 16.0.4305.5 · KB5126934 | Microsoft (MSRC) |
| Microsoft SQL Server 2022 for x64-based Systems (GDR) | 16.0.1210.3 · KB5128493 | Microsoft (MSRC) |
| Microsoft SQL Server 2025 for x64-based Systems (CU9) | 17.0.5015.4 · KB5126967 | Microsoft (MSRC) |
| Microsoft SQL Server 2025 for x64-based Systems (GDR) | 17.0.1145.4 · KB5128492 | Microsoft (MSRC) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
- Published
- Fix recordedsame day
- TodayNov 13, 2026+31 d
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
- CVE-2026-6681328 days apartMicrosoft SQL Server Elevation of Privilege Vulnerability32Monitor
- CVE-2026-858880 days apartMicrosoft SQL Server Information Disclosure Vulnerability30Monitor
- CVE-2026-11693228 days apartMicrosoft SQL Server Information Disclosure Vulnerability26Monitor
- CVE-2026-11810328 days apartMicrosoft SQL Server Information Disclosure Vulnerability26Monitor
- CVE-2026-11693928 days apartMicrosoft SQL Server Information Disclosure Vulnerability22Monitor
- CVE-2026-676280 days apartMicrosoft SQL Server Information Disclosure Vulnerability19Monitor
Not on record for this CVE: patch commit or PR link · researcher credit · public bounty program.
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- none
- Availability
- none
Impact can extend beyond the vulnerable component (scope changes).
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Changed
- Confidentiality impact
- High
- Integrity impact
- None
- Availability impact
- None
Weakness class (CWE)
CWE-125 · Out-of-bounds ReadCVSS vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
ATT&CK techniques
—
Change log
- Fix✗ → ✓
- SSVC exploitation— → none
- Exploit maturity— → none
For records you follow, these changes also arrive as notifications. →
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.