CVE-2025-24070HighMicrosoft CVSS 7.0CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:H/E:U/RL:O/RC:C

Microsoft security update for CVE-2025-24070

Published
July 11, 2026
Last Modified
—

🔗 CVE IDs covered (1)

CVE-2025-24070 →

📋 Microsoft's advisory

EchelonGraph does not copy Microsoft's advisory page: its FAQ and remediation text are not shown here. Read the advisory on https://msrc.microsoft.com/update-guide/vulnerability/CVE-2025-24070. This page also shows what EchelonGraph holds for CVE-2025-24070, with the description from its CVE record, which the CVE Numbering Authority that assigned the CVE wrote: for a CVE Microsoft assigned, often in the words of Microsoft's own advisory.

🎯 Affected products6

  • ASP.NET Core 8.0
  • ASP.NET Core 9.0
  • Microsoft Visual Studio 2022 version 17.10
  • Microsoft Visual Studio 2022 version 17.12
  • Microsoft Visual Studio 2022 version 17.13
  • Microsoft Visual Studio 2022 version 17.8

✅ Updates Microsoft lists: 6 updates

6 rows: one per KB article or update, update type and fixed build. Their details are on Microsoft's advisory.

KB articleUpdateFixed build
—Security Update8.0.14
—Security Update9.0.3
—Security Update17.12.6
—Security Update17.13.3
—Security Update17.8.19
—Security Update17.10.12

🧭 EchelonGraph on CVE-2025-24070

EchelonGraph score
7.0 HIGH
CISA KEV
Not listed
Fix status
A fix is available — apply it.

Description from the CVE record (CVE.org), as published by its numbering authority

Weak authentication in ASP.NET Core & Visual Studio allows an unauthorized attacker to elevate privileges over a network.

Published by Microsoft Corporation, the CVE Numbering Authority that assigned CVE-2025-24070, in its CVE record at CVE.org; reused under the CVE Program's Terms of Use (its licence and MITRE's copyright notice are in our Terms of Service).

🔗 References (10)