Microsoft Paint vulnerability needs a Store app update
The Microsoft Paint vulnerability tracked as CVE-2026-83844 now has a fix in the Microsoft Store, but Windows Update will not deliver it. The flaw can enable remote code execution, meaning an attacker could make vulnerable software run their commands from elsewhere on a network. Paint must instead reach build 11.2609.401.0 through a Store update.
The Hacker News found that 11.2609.401.0 was the newest Paint build offered in all ten countries it checked. Earlier in the week, device-management software maker RFF checked the Store in six countries and found that each was still offering 11.2605.81.0, which does not contain the fix. RFF's test virtual machine, a software-based computer used for testing, subsequently updated itself to the fixed build through Store auto-update. That result covers only one machine, however, and it remains unclear how quickly the update will reach other PCs.
CVE-2026-83844 is an out-of-bounds read, an error in which software reads data beyond the part of memory it was supposed to use. Microsoft says the weakness could allow code execution over a network and rates it Important, with a CVSS score of 8.1. CVSS, or the Common Vulnerability Scoring System, is a standard method for expressing the severity of a security flaw. According to Microsoft, exploiting this Paint vulnerability successfully would require a deep understanding of the targeted system.
Microsoft's advisory says an attacker could exploit the flaw by sending a specially prepared network packet to an affected service. A packet is a small unit of data sent across a network. The advisory does not identify which service is involved. An attack would not require the attacker to sign in, and the user would not need to click or otherwise assist. When Microsoft published the vulnerability on October 13, it was not known to have been publicly disclosed or exploited.
There is an important version discrepancy for security teams and vulnerability scanners. Microsoft's security advisory identifies 11.2609.401.0 as the fixed build. However, the CVE record published by Microsoft still describes only Paint versions below 11.2605.91.0 as affected, and the NVD entry shows the same range. NVD, the National Vulnerability Database, is a public collection of information about documented security flaws.
As a result, a scanner that relies on the CVE record could classify any Paint build from 11.2605.91.0 onward as secure, even though the current advisory names the later 11.2609.401.0 build as the fix. A system running 11.2609.401.0 or later satisfies both thresholds. According to a question posted on Microsoft Q&A, the advisory itself still named 11.2605.91.0 as the fixed build as recently as last week. Its revision history shows only the October 13 entry and does not record the version change.
Checking Paint for only the person currently signed in is not sufficient. Like other Store apps, Paint is installed separately for each user account on a PC. Windows may also retain a provisioned copy, which is the package automatically installed when a new user signs in. Older vulnerable copies can therefore remain under other accounts or in that provisioned package.
RFF's test write-up provides two commands for an administrator to run in PowerShell, a Windows tool for managing the computer with typed instructions. The first lists Paint versions belonging to every user, while the second checks the provisioned copy:
Get-AppxPackage -AllUsers -Name Microsoft.Paint | Select-Object Version, @{ n = 'Users'; e = { $_.PackageUserInformation.UserSecurityId.Username -join ', ' } }
Get-AppxProvisionedPackage -Online | Where-Object DisplayName -eq 'Microsoft.Paint' | Select-Object Version
If either command reports a version below 11.2609.401.0, Paint should be updated through the Store or allowed to receive the fixed build through Store auto-update. In Intune and other device-management tools, a Store app update scan can perform this process across multiple PCs. Administrators should then run both commands again and confirm that every installed and provisioned copy reports 11.2609.401.0 or later.
Microsoft's advisory lists no workaround or mitigation. Before the corrected build became available through the Store, RFF suggested removing Paint from systems where nobody needed it, including every user's copy and the provisioned package. RFF did not test that removal procedure. For organisations reviewing software-update practices across managed PCs, AEU-I provides security-first IT, infrastructure and consulting.
The vulnerability was not listed in the U.S. Cybersecurity and Infrastructure Security Agency's Known Exploited Vulnerabilities catalog when The Hacker News checked it. That catalog, which identifies flaws known to have been used in attacks, had last been updated earlier in the week. The absence of CVE-2026-83844 from the catalog does not replace checking the installed build, particularly because the advisory and CVE record currently give different fixed-version thresholds.