← All posts

MS Paint Has an RCE — and Patch Tuesday Can't Fix It

CVE-2026-83844 is an 8.1 RCE in Windows 11 Paint, and the fix ships only through the Microsoft Store — so a fully patched fleet can still be running the vulnerable build. Here's how to find it.

A drawing app got an RCE, and your patch dashboard stayed green

Microsoft Paint now has a remote code execution vulnerability — CVE-2026-83844, an out-of-bounds read (CWE-125) in the Windows 11 Paint app, scored CVSS 8.1. Microsoft's advisory says an unauthenticated attacker could run code over the network, with no sign-in and no user interaction required. And here is the part that should worry every Windows admin: the October cumulative update never touched it. The fix ships only through the Microsoft Store.

That makes this CVE a case study in a blind spot most fleets don't know they have. Your Patch Tuesday dashboard can show 100% compliant while every machine on it runs a vulnerable build of an app that ships with the OS.

What happened, in order

Microsoft rates exploitation as "less likely," attack complexity as high, and the flaw is not on CISA's Known Exploited Vulnerabilities list. No exploit or proof of concept has been published. None of that changes the structural lesson: there is nothing to block yet, and also nothing in your normal patch workflow that would have caught this.

Two update lanes, and only one carries the fix

Windows 11 Paint is a Store app. Your monthly cumulative update patches the OS; Paint updates on its own track, one user profile at a time. That is the whole gap:

Paint is not the only app in this position — it is just the one that got a CVE this month. Every Store app on your machines lives in lane 2: Calculator, Photos, Terminal, Notepad, the Snipping Tool. The October Patch Tuesday was a record-breaker — 1,407 unique CVEs, 78 of them Critical, including the exploited Windows Shell zero-day CVE-2026-96951 — and it is worth remembering that all of that volume still only covers lane 1. An auditor that checks "is the OS patched?" answers a different question from "is this machine actually running vulnerable software?"

How to check your machines right now

Don't trust the patch dashboard for this one. Check the app itself:

# Current user
Get-AppxPackage Microsoft.Windows.MSPaint |
    Select-Object Name, Version

# Every profile on the machine — Store apps install per user
Get-AppxPackage -AllUsers Microsoft.Windows.MSPaint |
    Select-Object Name, Version, PackageUserInformation

Anything below 11.2609.401.0 is vulnerable. If the version comes back older and Store updates are disabled by policy, the machine will stay vulnerable until someone either re-enables Store updates or deploys the fixed package another way. That is a policy decision worth revisiting: the GPO that blocks the Store to reduce attack surface is now the same GPO blocking a security fix from arriving.

The WinSentinel angle

This is exactly the class of problem WinSentinel is built to catch. On a single machine, WinSentinel's audit modules inspect what is actually installed and configured — not what the patch dashboard claims. Run the audit, and the machine in front of you tells you the truth about itself: every module, no limits, on that one machine. That is the free tier doing its job.

Across a fleet, the question changes shape. One machine's Paint version is a curiosity; a hundred machines' Paint versions, rolled up centrally with the outliers flagged, is a compliance picture — and that is where fleet orchestration comes in. WinSentinel Pro's central node aggregates audit results across the fleet, so a Store-app gap like this one shows up as a drift alert on the machines that missed the update, instead of hiding behind a green patch dashboard.

The broader lesson from October is that patching is two jobs, not one. The OS lane is mature, automated, and well-measured. The app lane is per-user, policy-gated, and largely invisible to the tools that report on the first lane. If your audit only ever asks the OS whether it is patched, you are auditing half the machine. Ask the machine itself — and ask all of them, in one place.

The fix for CVE-2026-83844 has existed for weeks. The question is not whether Microsoft shipped it. The question is whether your fleet actually received it — and whether anything you run would tell you if it hadn't.