Most Windows administrators trust Patch Tuesday to take care of the operating system. CVE-2026-83844 is a reminder that some of the software built into Windows is no longer patched that way. The flaw is in Windows Paint, the image editor that ships with Windows 11. Microsoft published it on Oct. 13, 2026, and the fix comes only through the Microsoft Store. Windows Update does not deliver it.

That would just be an inconvenience if the fix had arrived cleanly. It did not. Early this month, a Windows Latest editor with automatic Store updates turned on found no Paint update waiting, and IT admins on Reddit said the same. The public records have also disagreed about which Paint build is fixed, how severe the bug is and how it can be attacked. Some of those records changed as recently as this weekend.

The bug, in plain terms

Microsoft's CVE record titles the flaw "Windows Paint Remote Code Execution Vulnerability." The National Vulnerability Database (NVD), the U.S. government's catalog of CVEs, describes it as an out-of-bounds read that "allows an unauthorized attacker to execute code locally." An out-of-bounds read means the program reads memory outside the buffer it was supposed to use. NVD files it under CWE-125, the standard weakness category for that mistake. Bugs like this are usually triggered by malformed input, and a skilled attacker can sometimes turn one into control of the program.

Both the NVD entry and the CVE.org record list Microsoft Paint versions from 11.0.0.0 up to, but not including, 11.2609.401.0 as affected. NVD's entry was last modified on Nov. 8 and still shows a status of "Undergoing Analysis." The CVE.org record, which Microsoft maintains as the assigning authority, was last updated on Nov. 7.

Three questions the records don't answer the same way

Which build is fixed?

The current answer is 11.2609.401.0. The NVD and CVE.org records list it as the first unaffected version, and The Hacker News reported on Nov. 6 that it was the newest build offered in all ten countries it checked. Windows Latest also cites Microsoft's support documentation as saying 11.2609.401.0 or newer is patched.

It wasn't always that clear. According to The Hacker News, on Nov. 6 Microsoft's advisory named 11.2609.401.0 as the fixed build, but the CVE record and the NVD entry still listed Paint as affected only below 11.2605.91.0. The same report says the advisory itself gave 11.2605.91.0 as the fixed build as recently as the week before, according to a question on Microsoft's Q&A forum. Brian Vitko of RFF, a device-management software maker, found the Store offering 11.2605.81.0 as the newest build in six countries earlier that week. His test virtual machine later updated itself to the fixed build through Store auto-update, though The Hacker News stressed that this was one machine and it was unclear how quickly other PCs would follow. Both 11.2605 builds are below the version the records now treat as the cutoff. A machine that someone confirmed as "patched" against the earlier 11.2605.91.0 number may therefore still be vulnerable.

Did the fix actually reach people?

Not always. On Nov. 5, Mayank Parmar of Windows Latest wrote that he found no Paint update in the Microsoft Store even though automatic updates were on, and that his copy was running 11.2603.251.0. He also reported that IT admins on Reddit said they could not see the update either, even when they used a third-party tool to download the app package. Windows Latest said it did not know whether a bug was hiding the fixed build or whether Microsoft had documented an incorrect version. The Hacker News reported the next day that the fixed build was available. Machines that checked during the gap could have ended up on an older build.

How bad is it, and how is it attacked?

This is where the sources disagree most. The NVD and CVE.org records give a CVSS 3.1 base score of 7.0 (High). Their vector describes a local attack (AV:L) with high attack complexity (AC:H), no privileges required (PR:N), and user interaction required (UI:R). If the vector is accurate, someone has to open or handle something malicious on the target PC, and the attack isn't easy to pull off. The CVE.org vector also marks exploit maturity as "unproven" and says an official fix exists.

The Hacker News and Windows Latest report a different picture. The Hacker News says the advisory rates the bug Important with a CVSS score of 8.1, and that exploitation requires a specially crafted network packet with no sign-in and no help from the user. The advisory, as quoted, does not name the network service involved. Windows Latest's headline also calls it a "no-click" bug, though it adds that Microsoft describes the flaw as difficult to exploit. We could not read Microsoft's own advisory page directly because it is a JavaScript application, so we cannot say which description it shows today. What we can say is that the machine-readable records were updated after The Hacker News published, and they now describe a local attack that needs user interaction.

Until Microsoft explains the difference, defenders should plan for the worse of the two descriptions. Patching Paint takes little effort either way.

Is anyone exploiting it?

No source reports active exploitation. The Hacker News says the flaw was not known to be exploited or publicly disclosed when it was published on Oct. 13, and that it was not in CISA's Known Exploited Vulnerabilities (KEV) catalog when the outlet checked on Nov. 6. Windows Latest likewise saw no reports of exploitation in the wild. CISA has also scored the bug with SSVC (Stakeholder-Specific Vulnerability Categorization), its triage system, and that entry appears in the NVD record. It lists exploitation as "none" and automatable as "no," but technical impact as "total." In other words, CISA saw no attacks when it scored the bug on Oct. 13, but a successful attack would give the attacker full control of the affected component.

Why a Store-only fix matters

On Windows 11, Paint is a Store app, and the Store updates it separately from the operating system's monthly updates. Windows Latest notes that installing the October 2026 Windows update does not necessarily protect you from this flaw, because Paint is maintained through the Store. The Hacker News notes two more points that matter for administrators. Paint is installed separately for each user account, and Windows can also keep a provisioned copy, which is a version it installs for each new user. A check of only the signed-in account can miss older copies, so one user profile showing the new build doesn't prove the whole machine is fixed. It is reasonable to infer that patch-compliance tools that only track Windows Update could miss the problem, though neither source tests that. The advisory lists no workaround or mitigation.

What It Means for Defenders

  • Who is affected: any Windows system with Microsoft Paint between 11.0.0.0 and anything below 11.2609.401.0, according to the NVD and CVE.org records. That covers the 11.2605.81.0 and 11.2605.91.0 builds that were offered or described as fixed earlier.
  • The fixed version: Paint 11.2609.401.0 or later, delivered through the Microsoft Store. Windows Update does not install it, and installing the October 2026 cumulative update does not by itself fix this flaw.
  • Check every profile and the provisioned copy: because Paint installs per user, inventory the package across all users and check the provisioned package as well. The Hacker News points to PowerShell's Get-AppxPackage cmdlet with its all-users option, and to Get-AppxProvisionedPackage, for this. Any copy below 11.2609.401.0 still needs updating.
  • Re-verify earlier "patched" results: if your team signed off against 11.2605.91.0 based on the earlier advisory wording or the earlier CVE record range, check those machines again against the current threshold.
  • Don't rely on auto-update alone: Windows Latest's editor had automatic Store updates on and still saw no Paint update, and admins he cited reported the same missing update. Confirm the installed version.
  • Prioritize with the higher score in mind: the official records say 7.0, local, user interaction required. Reporting on the advisory says 8.1, network, no user interaction. Until those are reconciled, don't push this to the bottom of the queue just because it's Paint.
  • Watch for changes: NVD's analysis is still open, and the bug was not in KEV when The Hacker News checked. If CISA adds it or Microsoft revises the vector again, reassess.
  • No workaround: none is listed. Updating is the only mitigation the sources give.

Sources