SQL Server 2017 vulnerabilitiesRanked by how likely they are to be used.
SQL Server 2017 is made by Microsoft. We track 88 published vulnerabilities listed under that exact name, across 57 versions. None of them is on the list of flaws known to be exploited today. Microsoft lists newer releases under their own names, such as SQL Server 2017 Reporting Services, so check those pages too.
We keep watching the known-exploited list.
Is SQL Server 2017 listed under other names? Yes.
Microsoft also lists SQL Server 2017 under more specific names, such as SQL Server 2017 Reporting Services. Flaws listed only under those names are counted on their own pages, not here. If you run one of these, open its page for its own exploited flaws.
Which SQL Server 2017 vulnerabilities are being exploited?
This is the list that matters most: flaws criminals are using now.
None of SQL Server 2017's published vulnerabilities is on the list of flaws known to be exploited today. We keep watching that list.
Which SQL Server 2017 flaws are most likely to be used?
Ranked by the latest exploit-likelihood forecast: the chance each flaw is used in an attack in the next 30 days. A high severity score on its own doesn't tell you that. Flaws shared by many other makers' products are left out.
- 15%CVE-2025-49719High
Improper input validation in SQL Server allows an unauthorized attacker to disclose information over a network.
- 2.2%CVE-2024-37966High
Microsoft SQL Server Native Scoring Information Disclosure Vulnerability
- 1.9%CVE-2024-35271High
SQL Server Native Client OLE DB Provider Remote Code Execution Vulnerability
- 1.9%CVE-2024-37331High
SQL Server Native Client OLE DB Provider Remote Code Execution Vulnerability
- 1.9%CVE-2024-37318High
SQL Server Native Client OLE DB Provider Remote Code Execution Vulnerability
- 1.9%CVE-2024-37332High
SQL Server Native Client OLE DB Provider Remote Code Execution Vulnerability
- 1.9%CVE-2024-21414High
SQL Server Native Client OLE DB Provider Remote Code Execution Vulnerability
- 1.9%CVE-2024-35272High
SQL Server Native Client OLE DB Provider Remote Code Execution Vulnerability
- 1.9%CVE-2024-21398High
SQL Server Native Client OLE DB Provider Remote Code Execution Vulnerability
- 1.8%CVE-2024-21333High
SQL Server Native Client OLE DB Provider Remote Code Execution Vulnerability
Running SQL Server 2017? We'll keep checking.
Looking flaws up one at a time doesn't scale. Tell us what you run once, and we tell you which flaws matter to you, in what order, and keep watching for new ones.
- Tell us what you runPick your software from a list, or let us work it out from your website.
- We match it to every flawOver 400,000 published flaws, checked against your list.
- Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
- Told as soon as we knowAn alert by email, in the app or by webhook to your own tools.
Free plan, no card needed. Nothing to install.
1 new flaw affects software Acme tracks
Improper input validation in SQL Server allows an unauthorized attacker to disclose information over a network.
- Matched to
- SQL Server 2017 on Acme's software list
- What to do
- Plan in the vendor’s update
Sent to the alert recipients Acme chose. Also in the app and to Acme's webhook.
We track 88 published vulnerabilities listed under the name SQL Server 2017, across 57 versions.
None of SQL Server 2017's vulnerabilities is on the list of flaws known to be exploited today.
Microsoft also lists SQL Server 2017 under more specific names, such as SQL Server 2017 Reporting Services. Flaws listed only under those names are counted on their own pages, not here. Open the release you run to see its own list.
Create a Precursor Intelligence account and track SQL Server 2017. We match it against every published flaw, give each one a risk score from 0 to 100 and keep watching, so you hear about new ones as soon as we know, by email, in the app or by webhook.