How to Fix CVE-2024-26169: Privilege Escalation in Windows 10 Version 1809

By Sai Kiran Pandrala

Patch immediately. CISA added CVE-2024-26169 to the Known Exploited Vulnerabilities catalog on 2024-06-13. Federal civilian agencies must remediate by 2024-07-04. Treat every internet-reachable instance as a priority patch.

What is CVE-2024-26169?

CVE-2024-26169 is a Privilege Escalation flaw in Microsoft Windows 10 Version 1809. It carries a CVSS base score of 7.8 (high). CISA confirmed real-world exploitation by adding it to the Known Exploited Vulnerabilities catalog on 2024-06-13.

From the source record: Windows Error Reporting Service Elevation of Privilege Vulnerability

Why it matters in practice: KEV-listed CVEs draw continuous internet-wide scanning. Any unpatched, internet-reachable installation is on borrowed time. The blast radius depends on how the affected service is exposed. An internet-facing instance with no compensating controls is the highest-risk configuration.

Am I affected?

You are affected if your installation of Windows 10 Version 1809 matches a version listed in the Affected row above.

On Windows, check the installed version with PowerShell:

# Generic - list installed product versions
Get-CimInstance Win32_Product | Where-Object Name -like "*Windows 10 Version 1809*" | Select-Object Name, Version
# Windows updates installed (KB lookup)
Get-HotFix | Sort-Object InstalledOn -Descending | Select-Object -First 20

How to fix CVE-2024-26169

Apply the vendor patch. Target a build at or above: 10.0.10240.20526, 10.0.14393.6796, 10.0.17763.5576, 10.0.19044.4170, 10.0.19045.4170 (see advisory). The runnable command set below covers the most common deployment patterns for Windows 10 Version 1809.

Windows (PowerShell, run as administrator)

# 1) Backup affected service config
$stamp = Get-Date -Format yyyyMMdd-HHmm
$backup = "C:\Backup\windows-$stamp"
New-Item -ItemType Directory -Path $backup -Force | Out-Null

# 2) Install the latest Windows security updates (the patch for CVE-2024-26169 ships here)
Install-Module PSWindowsUpdate -Force -Scope CurrentUser -ErrorAction SilentlyContinue
Import-Module PSWindowsUpdate
Get-WindowsUpdate -MicrosoftUpdate -AcceptAll -Install -AutoReboot

# 3) Confirm the patch landed
Get-HotFix | Sort-Object InstalledOn -Descending | Select-Object -First 10

Vendor-managed app on Windows (winget)

# Vendor advisory: https://msrc.microsoft.com/update-guide/vulnerability/CVE-2024-26169
winget upgrade --all --silent --accept-package-agreements --accept-source-agreements
# or target the specific package:
winget search "Windows 10 Version 1809"
winget upgrade --id <PackageId> --silent

Complete PowerShell patch script

# Patch Windows 10 Version 1809 for CVE-2024-26169
$log = "C:\Backup\CVE-2024-26169-patch.log"
"[{0}] Starting patch run" -f (Get-Date) | Tee-Object -FilePath $log -Append
try {
    $stamp = Get-Date -Format yyyyMMdd-HHmm
    $backup = "C:\Backup\windows-$stamp"
    New-Item -ItemType Directory -Path $backup -Force | Out-Null
    # Backup hook - tailor for the product
    # Copy-Item "C:\Program Files\Windows 10 Version 1809" $backup -Recurse -ErrorAction SilentlyContinue

    if (-not (Get-Module -ListAvailable PSWindowsUpdate)) {
        Install-Module PSWindowsUpdate -Force -Scope CurrentUser
    }
    Import-Module PSWindowsUpdate
    Get-WindowsUpdate -MicrosoftUpdate -AcceptAll -Install -AutoReboot:$false -IgnoreReboot
    "[{0}] Updates installed" -f (Get-Date) | Tee-Object -FilePath $log -Append
    # Verify
    Get-HotFix | Sort-Object InstalledOn -Descending | Select-Object -First 5 | Out-File $log -Append
    "[{0}] Patch run complete - reboot at next maintenance window" -f (Get-Date) | Tee-Object -FilePath $log -Append
} catch {
    "[{0}] ERROR: $_" -f (Get-Date) | Tee-Object -FilePath $log -Append
    exit 1
}

After applying the patch

1. Restart the service or device so the patched binary loads.
2. Confirm the running version matches the Fixed in row using the verification command below.
3. Rotate credentials and API keys that the affected service could access if the asset was exposed during the disclosure window.

If you can't patch immediately

Until the patch lands, narrow the attack surface with these runnable controls.

Restrict the affected service via Windows Firewall

# Replace -RemoteAddress with your trusted admin range
New-NetFirewallRule -DisplayName "Block CVE-2024-26169 inbound" -Direction Inbound -Action Block -Protocol TCP -LocalPort 445,3389,5985
New-NetFirewallRule -DisplayName "Allow CVE-2024-26169 admin range" -Direction Inbound -Action Allow -Protocol TCP -LocalPort 445,3389,5985 -RemoteAddress 10.10.10.0/24

Disable the vulnerable feature if the vendor advisory allows it

# Vendor advisory: https://msrc.microsoft.com/update-guide/vulnerability/CVE-2024-26169
# Example: stopping a non-essential Windows service
Stop-Service -Name <ServiceName> -Force
Set-Service -Name <ServiceName> -StartupType Disabled

Mitigations are temporary. Apply the vendor patch as soon as a maintenance window opens.

How to verify the fix worked

Confirm the patched build is the one actually running.

# Confirm KB / hotfix is present
Get-HotFix | Sort-Object InstalledOn -Descending | Select-Object -First 10
# Confirm product version
Get-CimInstance Win32_Product | Where-Object Name -like "*Windows 10 Version 1809*" | Select-Object Name, Version

Expected: the patched build named in Fixed in (10.0.10240.20526, 10.0.14393.6796, 10.0.17763.5576, 10.0.19044.4170, 10.0.19045.4170 (see advisory)) appears in the version column.

Also worth doing: pull recent log windows for any indicators of compromise listed in the vendor advisory, and re-run an authenticated vulnerability scan with up-to-date signatures.

Frequently asked questions

Related fixes

Other vulnerabilities in the same area that are worth patching alongside this one:

• How to Fix CVE-2024-38080: Integer Overflow in Windows Server 2022 — Integer Overflow in Windows Server 2022
• How to Fix CVE-2024-43468: SQL Injection in Microsoft Configuration Manager — SQL Injection in Microsoft Configuration Manager
• How to Fix CVE-2024-30051: Heap-based Buffer Overflow in Windows 10 Version 1809 , Heap-based Buffer Overflow in Windows 10 Version 1809
• How to Fix CVE-2024-21412: Protection Mechanism Failure in Windows 11 Version 21H2 , Protection Mechanism Failure in Windows 11 Version 21H2
• How to Fix CVE-2024-38213: Security Bypass in Windows 10 Version 1809 , Security Bypass in Windows 10 Version 1809

Is CVE-2024-26169 being exploited in the wild?

Yes. CISA added CVE-2024-26169 to the Known Exploited Vulnerabilities catalog on 2024-06-13. KEV listing means at least one confirmed real-world exploitation report exists.

Do I have to take downtime to patch?

For most Microsoft Windows 10 Version 1809 deployments, the patched build needs a service restart or device reboot. HA pairs and clusters can roll the upgrade by patching the standby first, failing over, then patching the former primary.

Will a WAF or IDS rule alone close CVE-2024-26169?

No. Network filters cut down opportunistic scans but they do not remove the flaw. The vendor patch is the only durable fix.

How quickly should I act on CVE-2024-26169?

Within the standard patch cycle if the asset is internal-only. Inside one to two weeks for any internet-facing instance, sooner if compensating controls are not in place.

References

• Official vendor advisory: https://msrc.microsoft.com/update-guide/vulnerability/CVE-2024-26169
• NVD entry: https://nvd.nist.gov/vuln/detail/CVE-2024-26169
• CISA KEV catalog: https://www.cisa.gov/known-exploited-vulnerabilities-catalog
• CISA KEV entry: "Microsoft Windows Error Reporting Service Improper Privilege Management Vulnerability" - added 2024-06-13, due 2024-07-04

*Assembled from the official vendor advisory, the NVD record, and the CISA KEV listing on 2026-05-25. Always confirm against the vendor advisory before applying changes in production.*