⚠ Reference material — not professional advice. Test in staging, back up first, verify against your specific version. Use your own judgment for your environment.
● Medium · CVSS 6.5

How to Fix CVE-2026-20872: Arbitrary File Read in Windows 10 Version 1607

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

*By Sai Kiran Pandrala*

⚡ At a glance
SeverityCVSS 6.5 - Medium
Actively exploited?Not currently listed in CISA KEV
Affected10.0.14393.0 < 10.0.14393.8783, 10.0.17763.0 < 10.0.17763.8276, 10.0.19044.0 < 10.0.19044.6809, 10.0.19045.0 < 10.0.19045.6809, 10.0.22631.0 < 10.0.22631.6491, 10.0.22631.0 < 10.0.22631.6491, and others
Fixed inSee vendor advisory
Type (CWE)CWE-73: External Control of File Name or Path

What is CVE-2026-20872?

CVE-2026-20872 is an arbitrary file read flaw in Windows 10 Version 1607. An authenticated or unauthenticated request can read files outside the intended path scope, exposing configuration, secrets, or other sensitive content. Vendor description: External control of file name or path in Windows NTLM allows an unauthorized attacker to perform spoofing over a network.

Why this CVE matters

Arbitrary file read against a management product almost always exposes credentials, session secrets, or configuration. Treat any disclosure of this kind as a credential-rotation event in addition to a patching event.

For deployments of Windows 10 Version 1607 that have been exposed to the public internet during the disclosure window, the operating assumption should be that scanning has already happened. Even where exploitation has not been publicly observed, scanning for the vulnerable fingerprint is cheap and routine. Patching closes the door; log review and credential rotation close out the rest of the response.

Am I affected?

You are affected if your installation matches any of these version ranges:

Check your installed version against the list above. If you cannot determine the version, treat the system as affected and follow the upgrade path below.

On Windows, check the product's installed version via Settings - Apps - Installed apps, or run Get-Package from PowerShell to enumerate installed versions.

How to fix CVE-2026-20872

  1. Read the vendor advisory in full: https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-20872
  2. Upgrade Windows 10 Version 1607 to the patched build listed in the vendor advisory.
  3. Back up the configuration (and database, where applicable) before upgrading.
  4. Apply the patch in a maintenance window. For HA pairs, upgrade the standby node first, fail over, then upgrade the former primary.
  5. Restart the affected service so the patched binary loads, then verify the new version (see verification section).

Windows (PowerShell, run as administrator)


# Confirm the patched build against the vendor advisory: https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-20872
# 1. Apply current Windows Updates - vendor patches ship as monthly rollups.
Install-Module -Name PSWindowsUpdate -Force -SkipPublisherCheck -Confirm:$false
Import-Module PSWindowsUpdate
Get-WindowsUpdate -AcceptAll -Install -AutoReboot

# 2. Verify the specific KB landed (replace KB number from the advisory).
Get-HotFix | Where-Object { $_.HotFixID -match 'KB' }

# 3. Confirm the running product version (target: 10.0.14393.8783).
Get-CimInstance Win32_Product | Where-Object { $_.Name -match 'Windows 10 Version 1607' } |
  Select-Object Name, Version

# Or for an MSU file from the Microsoft Update Catalog:
# wusa.exe C:\Patches\windows10.0-kb<id>-x64.msu /quiet /norestart
# shutdown /r /t 60

Verify the fix landed


# Confirm the patched build against the vendor advisory: https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-20872
# 1. Confirm the running version equals the advisory's fixed-in build.
#    (Use the platform-specific version probe from the commands above.)

# 2. Re-scan with your vulnerability scanner (Nessus, Qualys, Tenable, OpenVAS).
#    The scanner should no longer flag CVE-2026-20872 on the patched target.

# 3. Inspect recent service and kernel logs for crash-loops or rollback events.
journalctl --since "10 minutes ago" | tail -200
dmesg --since "10 minutes ago" | tail -100

If you cannot patch immediately

No official workaround exists beyond restricting network exposure to the affected component. Apply the vendor patch as the primary remediation.

How to verify the fix worked

If your installation was internet-reachable during the disclosure window, treat log review as part of the remediation rather than an optional follow-up. Look for unusually long URI paths containing traversal sequences, unexpectedly large responses from the affected endpoint, and outbound requests from the application to internal addresses or cloud-metadata endpoints. Treat any sensitive file the bug could disclose as exposed.

Frequently asked questions

Is CVE-2026-20872 being exploited in the wild?

Public exploitation has not been confirmed by CISA at the time of writing. Treat the patch as time-sensitive anyway; reports often lag actual abuse.

Will a WAF or IDS rule fully mitigate CVE-2026-20872?

No. Network-layer filters can reduce noise and slow opportunistic scanners, but they will not stop a determined attacker. The vendor patch is the only durable fix.

How long should I plan for the upgrade?

Typical vendor-documented upgrade windows for Windows 10 Version 1607 run from a few minutes to under an hour depending on cluster size. Test in a staging environment first and follow the vendor's documented HA upgrade order.

References

*This guide was assembled from the official vendor advisory, the NVD record, and the CISA KEV catalog entry on 2026-05-25. Always confirm against the vendor advisory before applying changes in production.*