KB5040940: Security update for SQL Server 2017, CU branch, July 2024. Native Client OLE DB flaws patched; unused Stretch DB components removed
The update addresses 37 Important vulnerabilities in the Native Client OLE DB Provider and removes unused Stretch DB components from Setup.
Does it affect you? Applies to: Systems running SQL Server 2017 that meet the prerequisite for this update. The listed standalone package is for x64.
For servers on the CU branch: they install cumulative updates, which also bring fixes beyond security. Servers on the GDR branch (security fixes only) get a separate update. Which branch am I on?
What changes
Removal 1 change
Stretch DB
- Unused Stretch DB components are removed from SQL Server Setup.1
Technical details
Data sheet · Security · Downloads · Components Click to collapse or expand
Data sheet
- Released
- 2024-07-09
- Classification
- Security Updates
- Type
- Cumulative update
- Servicing branch
- CU
- Restart
- Required
- Replaced by
- KB5042215
| Version | Build | Channel |
|---|---|---|
| 2017 | 14.0.3471.2 | General availability |
Security
| Vulnerability | Severity | CVSS |
|---|
The table lists the 0 exploited, publicly disclosed or critical vulnerabilities. See all 37 vulnerabilities →
Downloads (Microsoft Update Catalog)
Sources
Cited passages from Microsoft's official notes (1)
-
1.
Removes unused components from SQL Server Setup.
support.microsoft.com
Checked automatically: 8 of 8 checks passed, 1 quoted passage · compared with Microsoft's page on Oct 20, 2026
- Quotes found in the official pages: passed
- Numbers found in the sources: passed
- Vulnerabilities from the dossier only: passed
- Links to allowed domains only: passed
- Every official change covered: passed
- Readable plain text: passed
- Changes confirmed by the file list: passed
- Sources agree: passed
A second AI read the text against the sources: correctness 5/5, clarity 4/5, completeness 5/5. How we work
Published by The Update Bureau. Written with AI from Microsoft's own documents, checked by rules and a second AI. How we work · Report a mistake