November 22, 2026

Microsoft Addresses Critical Remote Code Execution Vulnerability in Windows Paint via Microsoft Store Update

Microsoft has officially released a definitive patch for CVE-2026-83844, a significant remote code execution vulnerability affecting the Windows Paint application. The update, which brings the application to version 11.2609.401.0, marks a critical step in securing a legacy tool that has transitioned into a modern, Store-managed application. Unlike traditional Windows security patches that are typically bundled into monthly "Patch Tuesday" cumulative updates and delivered via Windows Update, this particular fix is being distributed exclusively through the Microsoft Store. This shift in delivery mechanism introduces unique challenges for system administrators and highlights the evolving landscape of software maintenance within the Windows ecosystem.

The vulnerability, identified as an out-of-bounds read flaw, carries a Common Vulnerability Scoring System (CVSS) score of 8.1, categorizing it as "Important." If successfully exploited, the flaw could allow a remote attacker to execute arbitrary code on a target system. While Microsoft’s initial assessment suggested that a successful attack would require a sophisticated understanding of the target environment, the potential for remote exploitation without user interaction makes the flaw a priority for security teams. As of the latest reports, the vulnerability had not been publicly disclosed or exploited in the wild prior to its documentation by Microsoft on October 13, but the delayed rollout of the fix across different regions has sparked concerns regarding the consistency of Store-based security patching.

The Challenge of Synchronized Patch Delivery

The rollout of version 11.2609.401.0 has been closely monitored by security researchers and IT professionals. Recent checks across ten different countries confirmed that the fixed build is now the primary version available through the Microsoft Store. However, the path to this widespread availability was not immediate. Earlier investigations conducted by Brian Vitko, a researcher at the device-management software firm RFF, revealed a disjointed distribution phase. In a series of tests performed earlier this week across six countries, Vitko found that the Microsoft Store was still serving version 11.2605.81.0—a build that does not contain the necessary security fixes for CVE-2026-83844.

This discrepancy highlights a fundamental difference between the centralized nature of Windows Update and the decentralized, CDN-reliant nature of the Microsoft Store. While Windows Update allows for a more synchronized push of security binaries, the Store often relies on regional caches and staggered update schedules. For organizations managing thousands of endpoints, this lack of predictability can complicate compliance reporting and vulnerability management. Vitko’s own test environment eventually transitioned to the fixed build through the Store’s automatic update feature, but the timeline for this transition remains variable depending on local Store configurations and network settings.

The situation is further complicated by the way Windows handles application updates for different user profiles. Because Windows Paint is now treated as an "Appx" package, it is managed differently than standard Win32 applications. The update process is often tied to the active user session, meaning that if a device is shared among multiple users or has stale profiles, older, vulnerable versions of the application may persist on the disk even after an update appears to have been applied to the primary account.

Microsoft Paint RCE Fix Now Available, but Windows Update Won't Deliver It

Which Build Counts as Fixed

One of the most significant points of confusion regarding CVE-2026-83844 involves the specific version number required to mitigate the risk. Microsoft’s official security advisory currently points to version 11.2609.401.0 as the definitive fixed build. However, a look at the CVE record and the National Vulnerability Database (NVD) entry reveals a conflicting narrative. Both the CVE documentation and the NVD currently list the vulnerability as affecting versions of Paint "below 11.2605.91.0."