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

How to Fix CVE-2026-40403: Path Traversal 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 8.8 - High
Actively exploited?Not currently listed in CISA KEV
Affected10.0.14393.0 < 10.0.14393.9140, 10.0.17763.0 < 10.0.17763.8755, 10.0.19044.0 < 10.0.19044.7291, 10.0.19045.0 < 10.0.19045.7291, 10.0.22631.0 < 10.0.22631.7079, 10.0.22631.0 < 10.0.22631.7079, and others
Fixed inSee vendor advisory
Type (CWE)CWE-122: Heap-based Buffer Overflow

What is CVE-2026-40403?

CVE-2026-40403 is a path traversal flaw in Windows 10 Version 1607. The product fails to canonicalize or restrict file paths supplied by a remote caller, so .. sequences or absolute paths reach restricted parts of the filesystem. Vendor description: Heap-based buffer overflow in Windows Win32K - GRFX allows an authorized attacker to execute code locally.

Why this CVE matters

Path traversal flaws look low-impact on paper but routinely chain into full compromise. An attacker who can read arbitrary files often pulls configuration secrets, session databases, or private keys, and many traversal bugs also allow writes that drop a webshell into the document root.

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-40403

  1. Read the vendor advisory in full: https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-40403
  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).

Apply the Microsoft security update


# CVE-2026-40403 affects Windows 10 Version 1607. Affected build range: 10.0.14393.0 < 10.0.14393.9140.
# Fixed in build: 10.0.14393.9140.
# Vendor advisory: https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-40403

# 1. Check the current build on the host.
[System.Environment]::OSVersion.Version
Get-ComputerInfo | Select-Object OsName, OsVersion, OsBuildNumber

# 2. Install the cumulative + security rollup that ships the fix.
Install-Module -Name PSWindowsUpdate -Force -SkipPublisherCheck -Confirm:$false
Import-Module PSWindowsUpdate
Get-WindowsUpdate -AcceptAll
Install-WindowsUpdate -AcceptAll -AutoReboot

# 3. Verify the patched build is present.
[System.Environment]::OSVersion.Version
# The build number must be >= 10.0.14393.9140 for the patch listed in the advisory.


# Inventory missing patches across a Windows fleet via Ansible (winrm).
ansible windows -m win_updates -a "category_names=SecurityUpdates state=installed"


# Re-run the version check after reboot and log the result.
$log = "C:\Logs\CVE-2026-40403-fix.log"
New-Item -ItemType Directory -Force -Path (Split-Path $log) | Out-Null
$build = [System.Environment]::OSVersion.Version
"$(Get-Date -Format s) post-patch build: $build" | Out-File $log -Append

Verify the fix landed


# CVE-2026-40403 verification checklist.

# 1. Confirm the running version matches 10.0.14393.9140 (replace the version probe with
#    the platform-specific command shown above).

# 2. Re-scan the host with your vulnerability scanner (Nessus, Qualys, Tenable,
#    OpenVAS, Wazuh). The scanner must no longer flag CVE-2026-40403.

# 3. Inspect recent service and kernel logs for crash-loops or rollback events.
journalctl -u <service-name> --since "10 minutes ago"
dmesg --since "10 minutes ago"

# 4. Cross-check the running build against the vendor advisory:
#    https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-40403

If you cannot patch immediately

Block requests containing ../, ..%2f, or absolute path prefixes at a reverse proxy. Restrict access to the affected endpoint to trusted networks. Apply the patched build as the real fix.

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-40403 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-40403?

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.*