CVE-2026-108463HighMicrosoft CVSS 8.8CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H/E:U/RL:O/RC:C

Microsoft security update for CVE-2026-108463 — Windows 11

Published
October 13, 2026
Last Modified
—

🔗 CVE IDs covered (1)

CVE-2026-108463 →

📋 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-2026-108463. This page also shows what EchelonGraph holds for CVE-2026-108463, 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 products8

  • Windows 11 Version 24H2 for ARM64-based Systems
  • Windows 11 Version 24H2 for x64-based Systems
  • Windows 11 Version 25H2 for ARM64-based Systems
  • Windows 11 Version 25H2 for x64-based Systems
  • Windows 11 Version 26H1 for ARM64-based Systems
  • Windows 11 Version 26H2 for ARM64-based Systems
  • Windows 11 Version 26H2 for x64-based Systems
  • Windows 11 version 26H1 for x64-based Systems

✅ Updates Microsoft lists: 2 KB articles

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

KB articleUpdateFixed build
KB5127648Security Update10.0.26100.9711
KB5127648Security Update10.0.26200.9711
KB5127648Security Update10.0.26300.9711
KB5127646Security Update10.0.28000.3231

🧭 EchelonGraph on CVE-2026-108463

EchelonGraph score
8.8 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

Improper resolution of path equivalence in Windows SmartScreen allows an unauthorized attacker to bypass a security feature over a network.

Published by Microsoft Corporation, the CVE Numbering Authority that assigned CVE-2026-108463, 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 (5)