On November 6, 2026, The Hacker News reported that Microsoft’s advisory named Microsoft Paint 11.2609.401.0 as the fixed build for CVE-2026-83844 and that it was the newest version in a Microsoft Store check across 10 countries. RFF separately recorded the same version in the U.S. Store catalog at 04:14 UTC that day.
RFF’s November 5 query had recorded version 11.2605.81.0 in six markets. Its November 6 query covered the U.S., U.K. and Germany. NeoTeo’s earlier report on RFF’s Store checks has those separate catalog observations.
For a machine-level answer, check both Paint’s packages for user profiles and the package provisioned for new profiles.
What the reported Paint update addresses
The Hacker News described CVE-2026-83844 as an out-of-bounds read that could lead to remote code execution. It reported Microsoft’s severity rating as Important, with a CVSS score of 8.1.
The Hacker News also reported that Paint’s fix is delivered through Microsoft Store, rather than Windows Update. A Windows Update check alone does not identify the version of Paint installed on a PC.
Check every Paint package on the PC
Paint can have separate packages for individual user profiles and a provisioned package used for new profiles. An administrator can check both scopes in PowerShell. RFF’s procedure uses -AllUsers for the user-package query, then checks the provisioned package separately:
Get-AppxPackage -AllUsers -Name Microsoft.Paint | Select-Object Version
Get-AppxProvisionedPackage -Online | Where-Object DisplayName -eq 'Microsoft.Paint' | Select-Object Version
Compare the results with 11.2609.401.0, the build reported as fixed. If Microsoft Store offers a Paint update, install it and rerun both queries to inspect the package versions again.
Teradabu Channel’s Japanese-language tutorial demonstrates checking Paint package versions in PowerShell.
