CVE-2026-83844: Paint RCE fix needs the Store, not Windows Update
Key takeaways
- Paint's fix for CVE-2026-83844 comes only through a Microsoft Store update, so Windows Update will not deliver it
- Microsoft's advisory names build 11.2609.401.0 as fixed while the CVE record still says 11.2605.91.0
- Paint is installed per user, so checks must cover every account and the provisioned copy
Microsoft has released a fix for CVE-2026-83844, a remote code execution flaw in Windows Paint, but it arrives only as a Microsoft Store update. Windows Update will not deliver it, which means patch dashboards built around monthly Windows rollups can show a machine as current while an unfixed copy of Paint sits on it.
Paint is the subject here as much as the flaw: a bundled app whose servicing has moved out of the operating system's normal update channel. For IT teams, the real work is knowing which build every user on every PC is running.
What it does well
The fix itself is straightforward. Microsoft names build 11.2609.401.0 as the fixed version, and The Hacker News found it was the newest Paint build in all ten countries it checked. Brian Vitko of RFF, a device-management software maker, saw the opposite earlier in the week: in six countries the newest build the Store offered was 11.2605.81.0, which lacks the fix. His test virtual machine has since moved to the fixed build on its own through Store auto-update. That is one machine, and how quickly other PCs will follow is not yet clear.
The Store model has one real advantage: Paint can be patched without waiting for a Windows cumulative update. In Intune and other device-management tools, the Store app update scan can push the fixed build across many PCs. Microsoft also says a restart may be needed after the update.
The flaw is an out-of-bounds read (CWE-125), where code reads memory beyond the intended boundary. Microsoft rates it Important, with a CVSS score of 8.1 and a temporal score of 7.1. The advisory says an attacker could send "a specially crafted packet to an affected service over the network" with no sign-in and no user interaction. It does not name the service. Microsoft also rates attack complexity as high, meaning the attacker needs a deep understanding of the target system. Brandefense advises treating the "zero-click" label as a description of the CVSS vector, not a measure of how easy an attack is.
Exploitation is not known. Microsoft flags the flaw as neither publicly disclosed nor exploited and assesses exploitation as less likely. It was not in the US Cybersecurity and Infrastructure Security Agency's Known Exploited Vulnerabilities catalogue when checked. Readers unfamiliar with that list can see how to check the CISA KEV catalogue.
Where it falls short
The weak points are in the delivery and the paperwork.
Two fixed-build numbers. Microsoft's advisory names 11.2609.401.0. The CVE record, which Microsoft also publishes, and the NVD entry list Paint as affected only below 11.2605.91.0. A scanner reading the CVE record would treat anything from 11.2605.91.0 upwards as fixed. As recently as last week the advisory itself gave 11.2605.91.0 as the fixed build, according to a forum question on Microsoft Q&A. The advisory's revision history shows only its 13 October entry, with no note of the change. A copy at 11.2609.401.0 or later passes under both numbers, so that is the safe target.
Per-user installs. Paint, like other Store apps, is installed separately for each user account. Windows can also keep a provisioned copy, installed for each new user. Checking only the signed-in account can miss older copies.
No workaround. The advisory lists no mitigation. Vitko suggested removing Paint where nobody needs it, for every user and from the provisioned copy, but he did not test that step.
Slow-moving records. NVD showed the record as Undergoing Analysis, and the CVE record was last updated on 31 October 2026. Tools that depend on those feeds may lag behind the advisory.
How it compares
The comparison that matters is between servicing routes, not products.
| Route | Delivers the Paint fix? | Coverage | Practical note |
|---|---|---|---|
| Windows Update | No | Not applicable | A fully patched OS can still run vulnerable Paint |
| Microsoft Store auto-update | Yes | Per user, as the app updates | One test VM moved on its own; wider timing unknown |
| Intune or other device management | Yes, via the Store app update scan | Many PCs at once | Needs the Store reachable or updates staged |
| Remove Paint | Not a fix | Every user plus provisioned copy | Suggested by Vitko, untested |
Pricing and value
The update costs nothing. The expense is staff time: auditing every user profile, confirming the Store is not blocked, and re-verifying afterwards. Where the Store is blocked or updates are staged, Brandefense advises using software inventory to list Paint builds and push the update. There is no licence cost attached to the fix.
Who should use it
This is a patch, so the question is who should act first.
- Managed Windows estates, in the UK and the US alike. Run the audit across all accounts. These teams are the ones with shared machines, provisioned profiles and blocked Stores.
- Teams that rely on CVE-record scanners. Set the pass mark at 11.2609.401.0, not 11.2605.91.0.
- Small offices with a few PCs. Open the Store, check for updates and install the Paint update.
- Anyone worried about urgency. Microsoft assesses exploitation as less likely and flags it as not exploited, so Brandefense advises updating on the normal patch cycle without leaving it open.
Vitko's test write-up gives two PowerShell commands, run in a window opened as administrator. The first lists every user's copy:
Get-AppxPackage -AllUsers -Name Microsoft.Paint | Select-Object Version, @{ n = 'Users'; e = { $_.PackageUserInformation.UserSecurityId.Username -join ', ' } }
The second lists the provisioned copy:
Get-AppxProvisionedPackage -Online | Where-Object DisplayName -eq 'Microsoft.Paint' | Select-Object Version
For any copy below 11.2609.401.0, update Paint through the Store or let auto-update install it, then run both commands again and confirm every copy shows 11.2609.401.0 or later.
Verdict
Worth the time, for anyone running Windows PCs they are responsible for. The risk is rated Important and unexploited, and the fix is free, but the delivery route is the trap: Windows Update will not deliver the Paint fix, so a machine can look current while Paint stays vulnerable. Audit every account and the provisioned copy, aim for 11.2609.401.0 or later, and watch for Microsoft to reconcile the advisory and the CVE record.
Frequently asked questions
Does Windows Update fix the Paint flaw?
No. The fix for CVE-2026-83844 reaches Paint only as a Microsoft Store app update, not through Windows updates.
Which Paint build is fixed?
Microsoft's advisory names 11.2609.401.0. The CVE record lists builds below 11.2605.91.0 as affected, so 11.2609.401.0 or later satisfies both.
Is CVE-2026-83844 being exploited?
Microsoft flags it as not exploited and not publicly disclosed, and it was not in CISA's Known Exploited Vulnerabilities catalogue when checked.