Overview of CVE-2026-83844 in Microsoft Paint
A critical remote code execution (RCE) vulnerability, identified as CVE-2026-83844, has been discovered in Microsoft Paint. While a fix for this serious flaw is now available, its distribution through the Microsoft Store, rather than standard Windows Update channels, presents a significant challenge for timely remediation. The inconsistent rollout of this update, as highlighted by The Hacker News, means many systems may remain vulnerable despite the patch’s release.
This vulnerability is concerning because it could allow an attacker to execute arbitrary code over a network without requiring user interaction or authentication. Given Paint’s ubiquitous presence on Windows systems, security professionals must prioritize verifying the update status of this application across their environments.
Technical Details of the Remote Code Execution Flaw
CVE-2026-83844 is categorized as an out-of-bounds read vulnerability. This type of flaw can enable an attacker to read data outside of an allocated memory buffer, which can lead to information disclosure or, in severe cases like this, arbitrary code execution. Microsoft has rated the vulnerability as “Important” with a CVSS score of 8.1, indicating its high severity. According to the advisory, a successful attack necessitates “a deep understanding of the target system.” Crucially, at the time of its publication on October 13, the flaw was not known to be exploited in the wild or publicly disclosed, suggesting a limited window for defenders to apply the fix proactively.
The attack vector involves sending “a specially crafted packet to an affected service over the network.” This characteristic underscores the severity of the flaw, as it does not rely on social engineering or user intervention to facilitate exploitation. Therefore, understanding the affected builds and ensuring proper patching is paramount for system integrity.
The Challenges of Microsoft Paint Update Distribution
The primary concern surrounding CVE-2026-83844 is the unconventional update mechanism for Microsoft Paint. Unlike core operating system components, Paint is distributed as a Microsoft Store application, meaning its updates are managed independently of Windows Update. The fixed build is identified as 11.2609.401.0. However, reports indicate that the auto-update process via the Microsoft Store is not reliably delivering this fix to all machines, leading to a fragmented patching landscape.
Adding to the confusion, the CVE record and its NVD entry still list Paint as affected only below 11.2605.91.0, treating any build from 11.2605.91.0 upwards as fixed. This discrepancy could lead scanning tools to incorrectly report systems as patched when they are not, particularly if they are running a build between 11.2605.91.0 and 11.2609.401.0. Administrators relying solely on CVE database information for vulnerability assessments may therefore miss vulnerable installations. Furthermore, Microsoft’s security advisory revision history does not currently reflect previous changes in the stated fixed build number, contributing to potential misunderstandings.
Actionable Recommendations for CVE-2026-83844 Mitigation
Given the intricacies of this vulnerability and its patch distribution, immediate and thorough action is required to secure systems. Understanding the full scope of mitigation steps for Microsoft Paint RCE is essential.
Identifying Vulnerable Microsoft Paint Builds
Because Microsoft Paint installs separately for each user account and maintains a provisioned copy for new users, simply checking the signed-in user’s version may not reveal all vulnerable instances. To effectively how to check Microsoft Paint vulnerability CVE-2026-83844, security professionals should use PowerShell commands to inspect all installed versions. Brian Vitko of RFF provided the following commands:
- To list every user’s copy of Paint:
Get-AppxPackage -AllUsers -Name Microsoft.Paint | Select-Object Version, @{ n = 'Users'; e = { $_.PackageUserInformation.UserSecurityId.Username -join ', ' } } - To list the provisioned copy:
Get-AppxProvisionedPackage -Online | Where-Object DisplayName -eq 'Microsoft.Paint' | Select-Object Version
These commands, executed from an administrator PowerShell window, provide a comprehensive overview of Paint installations and their corresponding versions, allowing administrators to identify unpatched instances accurately.
General Patching and Removal Guidance
To address the Microsoft Paint update mechanism CVE-2026-83844 issues, defenders should take the following steps:
- Verify Auto-Updates: Ensure that Microsoft Store auto-updates are enabled and functioning correctly for all systems. While inconsistent, this remains the primary official channel for the fix.
- Manual Verification and Update: Proactively use the PowerShell commands above to check all Paint installations. If vulnerable builds are identified, manually trigger updates via the Microsoft Store or ensure the auto-update process completes successfully.
- Remove Unnecessary Installations: Where Paint is not required for operational purposes, consider removing it for all users and from the provisioned copy. This eliminates the attack surface entirely, as suggested by Vitko prior to the fix’s widespread availability. While not tested by Vitko, this is a sound security practice for non-essential software.
- Stay Informed: Monitor Microsoft’s security advisories and the NVD for any updates or clarifications regarding the fixed build versions to prevent misidentification of patched systems. The current discrepancy highlights the need for vigilance beyond automated scanning relying on potentially outdated CVE information.
Related: CVE-2026-72530: TrueConf Server Remote Code Execution, CVE-2026-33824: Microsoft IKE Double Free RCE Exploit