Microsoft has fixed a remote code execution flaw in Windows Paint, but the patch will not arrive through Windows Update — and many fully patched PCs may still be running the vulnerable app.
The flaw, tracked as CVE-2026-83844, is an out-of-bounds read in the Windows 11 Paint app that Microsoft rates 8.1 out of 10 and classes as Important. According to Microsoft's advisory, an unauthenticated attacker could exploit it by sending a specially crafted packet to an affected service over the network, potentially running code with the same rights as the person using Paint. Microsoft says a successful attack would need a deep understanding of the target system, and it rates exploitation as less likely. No public exploit code is known, and the flaw had not been exploited in the wild when the company disclosed it on October 13.
The fix lives in the Microsoft Store, not Windows Update
Paint on Windows 11 is a Microsoft Store app, so its updates travel on a separate track from the operating system. The monthly cumulative update that patches Windows itself never touches it. The only way to get the fix is to update Paint to build 11.2609.401.0 through the Microsoft Store — by opening the Store, checking for updates, letting auto-update do its work, or running winget upgrade --id 9PCFS5B6T72H --source msstore from a terminal.
That matters because Store updates install separately for every user profile on a machine. A PC can show as fully compliant with Windows Update while every person who signs into it still runs a vulnerable copy of Paint. The machines most likely to be left exposed are locked-down fleets, kiosks and shared PCs, where Store updates are often blocked by policy or simply never run. Administrators can push the update through Intune instead.
Microsoft's own records disagree on the fixed build
The rollout itself has been messy. Microsoft first named build 11.2605.91.0 as the fix in October, but that build never appeared in the public Store catalog — researchers checking the catalog in early November found the newest available build was still 11.2605.81.0, which does not contain the fix. In early November, Microsoft's security advisory quietly switched the fixed build to 11.2609.401.0, and that build finally landed in the Store on November 5-6. The Hacker News confirmed it was the newest Paint build in all ten countries it checked on November 6.
The public CVE record and its NVD entry still list only builds below 11.2605.91.0 as affected, so scanners reading that record may wrongly call a vulnerable machine fixed. The practical rule is simple: any Paint build below 11.2609.401.0 should be treated as vulnerable, whatever the CVE record says. Anyone who patched in October should check again.
What to do now
For home users, the fix is a minute's work: open the Microsoft Store, head to Library, and install updates — or just confirm Paint is on build 11.2609.401.0 or later. The flaw is not in CISA's Known Exploited Vulnerabilities catalog, and Microsoft lists no workaround or mitigation, so updating is the only defence. Classic Paint on Windows 10 is not listed as affected; only the Windows 11 Store app is in scope.
The episode is a reminder that the apps bundled with Windows no longer patch with Windows. As more system apps move to the Store, a green Windows Update status proves less and less about the software sitting on top of it.



