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.

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."
This discrepancy suggests that an earlier attempt to patch the flaw may have been superseded by the current 11.2609.401.0 release. Historical data from Microsoft’s own Q&A forums indicates that as recently as last week, the advisory itself cited version 11.2605.91.0 as the fixed build. For security scanners and automated vulnerability management tools that rely on the NVD or the CVE record for their definitions, this creates a potential "false negative" scenario. A scanner might identify version 11.2605.91.0 as safe based on the CVE record, while Microsoft’s most recent advisory suggests that only the higher 11.2609.401.0 build is fully protected.
Despite these changes, Microsoft’s official revision history for the advisory remains sparse. The entry still primarily reflects the original October 13 publication date, with no detailed notes explaining the shift in the recommended fixed version. This lack of transparency can be frustrating for IT administrators who require precise data to validate their security posture. To remain secure, experts recommend ensuring that all installations of Paint meet or exceed the 11.2609.401.0 threshold, as this version satisfies the requirements of both the older CVE listing and the updated MSRC advisory.
How to Check Every Copy of Paint
The architectural shift of Windows Paint from a static system component to a provisioned Microsoft Store app means that traditional file-version checks may be insufficient. In modern Windows environments, Paint is installed as a package that can exist in two states: as an installed package for specific users and as a "provisioned" package that Windows uses as a template to install the app for any new user who logs into the machine.
Security researchers emphasize that simply checking the version of Paint through the "About" menu while logged in as an administrator does not guarantee that the entire system is patched. If an older version remains in the provisioned cache or in the profile of an inactive user, the vulnerability technically remains on the system. To address this, Brian Vitko provided a methodology for comprehensive auditing using PowerShell. By running specific commands with administrative privileges, it is possible to gain visibility into every instance of the application across the entire operating system.
The first critical check involves auditing all user profiles. Using the Get-AppxPackage command with the -AllUsers flag allows administrators to see every version of Paint currently residing in any user directory on the machine. This is essential for identifying "drift," where one user may have an updated version while another does not. The second check targets the provisioned package via Get-AppxProvisionedPackage. This ensures that the "master copy" held by the operating system is also updated, preventing the vulnerability from being reintroduced every time a new user account is created.

In environments where these versions fall below the 11.2609.401.0 mark, manual intervention may be required if the Store’s auto-update mechanism has failed to trigger. Microsoft has not provided a manual download link for the patch, nor has it offered an offline installer, making the Microsoft Store the sole official channel for remediation.
Attack Conditions and Exploitation Status
The technical nature of CVE-2026-83844 involves a memory safety issue where the application reads data outside the intended buffer. According to Microsoft’s advisory, the exploitation of this out-of-bounds read occurs when a "specially crafted packet" is sent to an affected service over the network. Interestingly, the advisory does not specify which underlying service Paint interacts with to facilitate this network-based attack. However, the critical takeaway for defenders is that the attack requires no authentication and no user interaction, placing it in the category of "zero-click" potential vulnerabilities.
In a typical remote code execution scenario involving an image editor, one might expect the attack to require a user to open a malicious file. However, the description of a "specially crafted packet" over a network suggests a different vector, possibly involving how Paint handles networked resources or how it integrates with other Windows services that process image data.
Currently, the U.S. Cybersecurity and Infrastructure Security Agency (CISA) has not added CVE-2026-83844 to its Known Exploited Vulnerabilities (KEV) catalog. The catalog, which serves as a definitive list of flaws known to be actively used by threat actors, was last updated earlier this week without the inclusion of this Paint flaw. This suggests that while the risk is high due to the nature of the vulnerability, there is currently no evidence of widespread exploitation.
Microsoft has stated that there are no known workarounds or mitigations for this flaw. This means that users cannot simply disable a specific feature or change a registry setting to protect themselves; the only path to security is the installation of the updated build. In high-security environments where the Microsoft Store is disabled or restricted, researchers like Vitko have suggested that the only temporary safeguard is the complete removal of the Paint package from both the active user profiles and the provisioned image. While this step effectively eliminates the attack surface, it also removes a core utility that many users rely on for basic tasks.
As the fixed build continues to propagate through the Microsoft Store’s global network, the incident serves as a reminder of the complexities inherent in modern software delivery. For a tool as ubiquitous as Windows Paint, the transition to a Store-based update model brings the benefits of faster feature iterations but also introduces new hurdles for the synchronized deployment of critical security patches. Owners of Windows systems are encouraged to verify their current Paint version and ensure that the Microsoft Store is permitted to perform background updates to maintain protection against this and future vulnerabilities.
