Microsoft SQL Server Information Disclosure Vulnerability
Noroxi assessment
Priority: Monitor (action score 26/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.99% (FIRST EPSS); higher than 61.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 (CU 31) 14.0.3550.4; Microsoft SQL Server 2017 for x64-based Systems (GDR) 14.0.2130.4; Microsoft SQL Server 2019 for x64-based Systems (CU 32) 15.0.4490.9.
Low priority for now. Upgrade to Microsoft SQL Server 2017 for x64-based Systems (CU 31) 14.0.3550.4; Microsoft SQL Server 2017 for x64-based Systems (GDR) 14.0.2130.4; Microsoft SQL Server 2019 for x64-based Systems (CU 32) 15.0.4490.9 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
Buffer over-read in SQL Server allows an authorized attacker to disclose information over a network.
- Published
- Sep 8, 2026
- Updated
- Oct 8, 2026
- EPSS
- 0.9% · 61th percentile
- CWE
- CWE-126
Report tools
Action score
26
Monitor
Low priority for now.
- CVSS
- 26 / 40 · 6.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.9%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · microsoft
- 6.5
- 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:U/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.
Running WordPress? Scan your site free with WP Lens
Noroxi 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.
| Vendor | Product | CPE |
|---|---|---|
| microsoft | sql server 2017 | cpe:2.3:a:microsoft:sql_server_2017 |
| microsoft | sql server 2019 | cpe:2.3:a:microsoft:sql_server_2019 |
| microsoft | sql server 2022 | cpe:2.3:a:microsoft:sql_server_2022 |
| microsoft | sql server 2025 | cpe:2.3:a:microsoft:sql_server_2025 |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- microsoft sql server 2017before 14.0.2130.4
- microsoft sql server 201714.0.3006.16 and later · before 14.0.3550.4
- microsoft sql server 2019before 15.0.2190.7
- microsoft sql server 201915.0.4003.23 and later · before 15.0.4490.9
- microsoft sql server 2022before 16.0.1200.5
- microsoft sql server 202216.0.4003.1 and later · before 16.0.4275.2
- microsoft sql server 2025before 17.0.1135.8
- microsoft sql server 202517.0.4006.2 and later · before 17.0.4085.5
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 (CU 31)
- 14.0.0 and later · before 14.0.3550.4affected
Microsoft Microsoft SQL Server 2017 (GDR)
- 14.0.0 and later · before 14.0.2130.4affected
Microsoft Microsoft SQL Server 2019 (CU 32)
- 15.0.0.0 and later · before 15.0.4490.9affected
Microsoft Microsoft SQL Server 2019 (GDR)
- 15.0.0 and later · before 15.0.2190.7affected
Microsoft Microsoft SQL Server 2022 (CU 26)
- 16.0.0.0 and later · before 16.0.4275.2affected
Microsoft Microsoft SQL Server 2022 (GDR)
- 16.0.0 and later · before 16.0.1200.5affected
Microsoft Microsoft SQL Server 2025 (CU8)
- 17.0.0.0 and later · before 17.0.4085.5affected
Microsoft Microsoft SQL Server 2025 for x64-based Systems (GDR)
- 17.0.1050.2 and later · before 17.0.1135.8affected
Same product
microsoft: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-67631Microsoft SQL Server Remote Code Execution Vulnerability39Monitor
- CVE-2026-78442Windows OLE DB Remote Code Execution Vulnerability35Monitor
- CVE-2026-77487SQL Server Elevation of Privilege Vulnerability35Monitor
- CVE-2026-77486Microsoft SQL Server Remote Code Execution Vulnerability35Monitor
- CVE-2026-77483SQL Server Elevation of Privilege Vulnerability35Monitor
- CVE-2026-77482Microsoft SQL Server Remote Code Execution Vulnerability35Monitor
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 (CU 31) | 14.0.3550.4 · KB5122774 | Microsoft (MSRC) |
| Microsoft SQL Server 2017 for x64-based Systems (GDR) | 14.0.2130.4 · KB5122775 | Microsoft (MSRC) |
| Microsoft SQL Server 2019 for x64-based Systems (CU 32) | 15.0.4490.9 · KB5122772 | Microsoft (MSRC) |
| Microsoft SQL Server 2019 for x64-based Systems (GDR) | 15.0.2190.7 · KB5122773 | Microsoft (MSRC) |
| Microsoft SQL Server 2022 for x64-based Systems (CU 26) | 16.0.4275.2 · KB5122768 | Microsoft (MSRC) |
| Microsoft SQL Server 2022 for x64-based Systems (GDR) | 16.0.1200.5 · KB5122771 | Microsoft (MSRC) |
| Microsoft SQL Server 2025 for x64-based Systems (CU8) | 17.0.4085.5 · KB5122769 | Microsoft (MSRC) |
| Microsoft SQL Server 2025 for x64-based Systems (GDR) | 17.0.1135.8 · KB5122770 | 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.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
- CVE-2026-673930 days apartMicrosoft SQL Server Information Disclosure Vulnerability26Monitor
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
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
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- None
- Availability impact
- None
Weakness class (CWE)
CWE-126 · Buffer Over-readCVSS vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/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.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.