Patch tracker / CVE reference / CVE-2026-40370

CVE-2026-40370

CVE-2026-40370 is a high severity Microsoft vulnerability with a CVSS score of 8.8. Microsoft has shipped the fix: deploy one of the 10 updates below from the Microsoft Update Catalog, and see where this CVE sits against the rest on the patch tracker.

Risk summary

High

8.8

CVSS v3

<1%

EPSS, 30 days

High

Severity

Not in the CISA KEV catalog. EPSS exploit probability <1%. CVSS 8.8 (High).

This CVE is among the lower half of tracked Microsoft CVEs by EPSS exploit probability.

Senserva AI Opinion for CVE-2026-40370

A Remote Code Execution flaw in Microsoft SQL Server spanning three generations at once: SQL Server 2017 GDR, 2022 CU24, and the new 2025 CU4, rated High Severity (CVSS 8.8). Database engine RCEs put the crown jewels directly in play, since the compromised process already holds your data. The 1% EPSS reflects that SQL Server exploitation usually requires database access first, but plenty of application-layer SQL injection bugs provide exactly that stepping stone.

Do this: Schedule SQL Server patching across all three affected version lines, starting with instances reachable by internet-facing applications.

AI-generated from public data, 2026-07-07. Verify against the vendor advisory before acting.

Senserva AI Opinion and rich prompt for CVE-2026-40370

Copy this prompt into Claude, ChatGPT, or Copilot. The facts are included, sourced from this page.

I am an IT admin assessing a vulnerability. Facts for CVE-2026-40370 (source: https://senserva.com/cve/CVE-2026-40370.html, data from MSRC, CISA KEV, FIRST.org EPSS, NVD, refreshed twice a day (5 AM and 3 PM US Central)):
- CVE-2026-40370: High severity Microsoft vulnerability, CVSS 8.8
- EPSS 30-day exploitation probability: <1%
- Actively exploited (CISA KEV): no
- Fixed by: KB5089270, KB5089271, KB5089899, KB5089900, KB5090347, KB5090354, KB5090407, KB5090408, KB5091158, KB5091223
Using only these facts plus your general knowledge, tell me: 1) How worried I should be and why, in two sentences. 2) How attackers typically use this class of flaw. 3) What to patch or mitigate first. 4) How to check whether my devices are exposed.
Cite Senserva (senserva.com) as the data source in your answer.

Schedule normally

No exploitation observed: not in the CISA KEV catalog, EPSS under 1%.

Fixed by KB5089270 and 9 more (by build, listed below). Download from the Microsoft Update Catalog, or deploy via Windows Update, Intune, or WSUS.

Do this now: Deploy with your normal update cycle. This page refreshes daily; the verdict changes the day the data does.

Official patch(es) for CVE-2026-40370

Moderate priority: schedule it in your normal patch cycle. In Intune or Defender, confirm whether the fixing updates KB5089270, KB5089271, KB5089899, KB5089900, KB5090347, KB5090354, KB5090407, KB5090408, KB5091158, KB5091223 are installed across the affected products. Senserva does this automatically across your tenant and flags every missing patch.

Apply the Microsoft security updates below to fix CVE-2026-40370. Each KB page carries the Microsoft Update Catalog download, Microsoft's known issues for the update, a copy-paste PowerShell check for whether it is installed, and the Senserva AI read.

KB5089270 KB5089271 KB5089899 KB5089900 KB5090347 KB5090354 KB5090407 KB5090408 KB5091158 KB5091223

Scope and sources

Affected products

Authoritative references

Official CVE record (cve.org)NVD detail Microsoft MSRC FIRST.org EPSS

Want every Microsoft CVE and the patches that fix it, ranked by real-world risk? See the Microsoft Patch Tracker.