Patch tracker / CVE reference / CVE-2026-26130

CVE-2026-26130

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

Risk summary

High

7.5

CVSS v3

2.8%

EPSS, 30 days

High

Severity

Not in the CISA KEV catalog. EPSS exploit probability 2.8%. CVSS 7.5 (High).

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

Senserva AI Opinion for CVE-2026-26130

This is a Denial of Service flaw in ASP.NET Core spanning versions 8.0, 9.0, and 10.0, so any web app or API built on these runtimes can be knocked offline by a crafted request. Severity is High with a CVSS score of 7.8, but the EPSS exploit probability sits at 3 percent, it is not in CISA KEV, and there is no known ransomware use. The main risk is availability of your public facing services, not data theft or code execution.

Do this: Inventory your ASP.NET Core 8.0, 9.0, and 10.0 apps and apply the current Microsoft runtime patch to any internet exposed service first.

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

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

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-26130 (source: https://senserva.com/cve/CVE-2026-26130.html, data from MSRC, CISA KEV, FIRST.org EPSS, NVD, refreshed twice a day (5 AM and 3 PM US Central)):
- CVE-2026-26130: High severity Microsoft vulnerability, CVSS 7.5
- EPSS 30-day exploitation probability: 2.8%
- Actively exploited (CISA KEV): no
- Fixed by: KB5081276, KB5081277, KB5081278
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 3%.

Fixed by KB5081276 and 2 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-26130

Moderate priority: schedule it in your normal patch cycle. In Intune or Defender, confirm whether the fixing updates KB5081276, KB5081277, KB5081278 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-26130. 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.

KB5081276 KB5081277 KB5081278

Scope and sources

Affected products

Fixed by the same updates

CVE-2026-26131 CVE-2026-26127

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.