Back to vendor advisories
Microsoft Security Response CenterCVE-2026-69605

Microsoft Install Service Elevation of Privilege Vulnerability

HighVendor CVSS 7.0 / 10 1 CVE Published Sep 8, 2026 at 7:00 AM UTC

Summary

Use after free in Microsoft Install Service allows an authorized attacker to elevate privileges locally.

Products covered

  • Windows Server 2022

  • Windows Server 2022 (Server Core installation)

  • Windows 10 Version 21H2 for 32-bit Systems

  • Windows 10 Version 21H2 for ARM64-based Systems

  • Windows 10 Version 21H2 for x64-based Systems

  • Windows 10 Version 22H2 for x64-based Systems

  • Windows 10 Version 22H2 for ARM64-based Systems

  • Windows 10 Version 22H2 for 32-bit Systems

Show 10 more products
  • Windows Server 2025 (Server Core installation)

  • Windows 11 Version 25H2 for ARM64-based Systems

  • Windows 11 Version 25H2 for x64-based Systems

  • Windows 11 Version 23H2 for ARM64-based Systems

  • Windows 11 Version 23H2 for x64-based Systems

  • Windows 11 Version 24H2 for ARM64-based Systems

  • Windows 11 Version 24H2 for x64-based Systems

  • Windows Server 2025

  • Windows 11 version 26H1 for x64-based Systems

  • Windows 11 Version 26H1 for ARM64-based Systems

Remediation

Install KB5122882. Install KB5122878. Install KB5122871. Install KB5124008. Install KB5122880. Install KB5124012.

Vendor-listed fixes

  • 10.0.20348.5622

  • 10.0.19044.7725

  • 10.0.19045.7725

  • 10.0.26100.33438

  • 10.0.26200.9445

  • 10.0.22631.7582

  • 10.0.26100.9445

  • 10.0.28000.2954

CVEs in this advisory 1

Update history

What changed in later vendor updates

SecurityAlert records field-level changes from the point we begin following a bulletin. Earlier vendor changes may not have a field-by-field record.

    • The vendor changed the advisory's last-updated date.
    • The vendor changed the advisory's last-updated date.

Updates

  1. Published by Microsoft Security Response Center

    The publication date reported by the vendor.

  2. Added to SecurityAlert

    We collected the advisory from the official source.

  3. Updated by Microsoft Security Response Center

    The vendor changed the advisory after it was first published.

  4. Confirmed at the source

    Our collector saw this advisory during a later source check.