Microsoft has revised the required Paint build to 11.2609.401.0 for CVE-2026-83844, a remote code execution vulnerability. Its November 6 advisory revision says this new release is needed to “comprehensively address” the flaw. Check the installed application version separately from the operating system’s update status.
The Microsoft advisory originally appeared on October 13. The fresh development is its November 6 remediation revision, verified through Microsoft’s advisory data. A recent Hacker News submission does not make the original disclosure new.
Evidence status: vendor-confirmed vulnerability and revised fix, without reported exploitation in Microsoft’s current assessment. Microsoft marks exploitation “No” and assesses exploitation as less likely. That is its assessment at review time, not proof that every affected installation is safe.
The current version boundary supersedes early discussion
The current CVE record lists Microsoft Paint 11.0.0.0 up to, but excluding, 11.2609.401.0 as affected. Microsoft’s affected-product data names 11.2609.401.0 as the fixed build and links to the Microsoft Store app update.
The record describes an out-of-bounds read, access beyond an intended memory region, that can lead to code execution. Microsoft’s revised assessment describes a local attack requiring user interaction, with high attack complexity.
Update — November 7, 2026, 9:42 p.m. EST
Microsoft’s November 7 revision changes the attack vector and adds an FAQ. It now describes local execution requiring user interaction, rather than the unauthenticated network attack without interaction stated in the earlier version of this article. Microsoft gives a crafted file opened by a victim as an example, not a confirmed account of the specific exploit. The fixed build remains 11.2609.401.0.
The detailed delivery path remains undisclosed. The advisory does not establish that Paint must already be open, that thumbnail generation triggers the flaw, or that an AI feature causes it. Treat those explanations as speculation until technical evidence supports them.
Verify the application update actually arrived
For users with the affected app, obtain the Paint update through Microsoft’s listed Store channel and confirm build 11.2609.401.0 or later is installed. Microsoft’s Store update instructions explain manual update checks and managed update settings.
For administrators, inventory the Paint package version through existing management tools. Check whether Store-app update policies or blocked delivery paths leave devices behind. A successful operating-system update check alone does not verify this application’s repair.
The published range names the modern Paint app. It supplies no equivalent fixed-version table for every historical Paint executable. Match the actual product and package version rather than extrapolating from the Windows release name.
What the thread adds
The ranked Hacker News discussion exposes an operational gap between Windows updates and Store-app delivery.
greyhound1 reports: “Had to go to Microsoft Store to get the fixed version, Windows Update didn’t show anything.” gadrev, replying in that branch, similarly reports an update after opening Paint’s Store page. These are individual experiences; Microsoft’s update link independently supports checking the Store channel.
Other comments repeat an older fixed-version boundary or propose thumbnail and AI explanations. The current primary records resolve the build target, but leave those proposed attack mechanisms unverified. Neither comment volume nor a severity score supplies evidence of an active campaign.
From a 281-comment thread, in HN’s own order.
Caveat: Microsoft confirms the revised fix but gives little attack-path detail; its current exploitation assessment should not be mistaken for a measured absence of attacks.