Patch tracker / Products / Microsoft SQL Server 2017 (CU 31)

Microsoft SQL Server 2017 (CU 31): vulnerabilities and security updates

Every CVE affecting Microsoft SQL Server 2017 (CU 31) and the Microsoft update (KB) that fixes it, ranked by real-world risk. Actively exploited (CISA KEV) first, then EPSS exploit probability, on top of CVSS severity.

CVEs
12
Updates (KBs)
6
Actively exploited (KEV)
0
Critical Severity
0

CVEs affecting Microsoft SQL Server 2017 (CU 31)

CVESeverityCVSSEPSSStatus
CVE-2024-37338High8.82.2%-
CVE-2024-37335High8.82.2%-
CVE-2024-37340High8.82.2%-
CVE-2024-37339High8.82.2%-
CVE-2024-26186High8.82.2%-
CVE-2024-26191High8.82.2%-
CVE-2024-37965High8.82.2%-
CVE-2024-37980High8.82.2%-
CVE-2024-43474High7.62.2%-
CVE-2024-37966High7.12.2%-
CVE-2024-37337High7.12.2%-
CVE-2024-37342High7.12.2%-

Updates (KBs) for Microsoft SQL Server 2017 (CU 31)

UpdateReleasedSeverityCVSSEPSSCVEsStatus
KB50422112024-09-10High8.82.2%11-
KB50422142024-09-10High8.82.2%12-
KB50422152024-09-10High8.82.2%12-
KB50422172024-09-10High8.82.2%12-
KB50425782024-09-10High8.82.2%11-
KB50427492024-09-10High8.82.2%11-

Ranked across all products on the Microsoft patch tracker and the CVE and vulnerability management reference. Browse every product: product index.

Most searched on Senserva right now

New to a term on this page? CVE, KB, KEV, CVSS, and EPSS are each explained once, on the Senserva security lexicon. Reference: Microsoft CVE and vulnerability management and the Microsoft patching guide.
Provided as is, without warranty; verify against the vendor advisory before acting. Data notice and terms.