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.
