Skip to content
The Cybersecurity Focus
The Cybersecurity Focus

Cybersecurity news, threat intelligence, and vulnerability research.

The Cybersecurity Focus

Cybersecurity news, threat intelligence, and vulnerability research.

  • Home
  • Home
The Cybersecurity Focus

Cybersecurity news, threat intelligence, and vulnerability research.

The Cybersecurity Focus

Cybersecurity news, threat intelligence, and vulnerability research.

  • Home
  • Home
CVEVulnerabilityWindows

Microsoft Paint RCE CVE Store-Only Fix Leaves Windows Systems Vulnerable

By ogwatermelon
November 8, 2026 3 Min Read
0
November 8, 2026

Microsoft has patched a remote code execution flaw in Windows Paint, but the fix arrives only through the Microsoft Store. CVE-2026-83844 leaves systems vulnerable unless administrators verify that every user copy of Paint has updated. The vulnerability carries a CVSS score of 8.1 and could let an attacker run code across a network without user interaction.

What Happened: Microsoft Paint RCE Flaw Fixed via Store Update

On October 13, 2026, Microsoft disclosed CVE-2026-83844, an out-of-bounds read in Windows Paint that can lead to remote code execution. The flaw is rated Important and has a CVSS score of 8.1. Microsoft says a successful attack requires a deep understanding of the target system. At the time of disclosure, the flaw was not known to be exploited or publicly disclosed.

The fixed build is 11.2609.401.0, which is now available in the Microsoft Store across all regions that The Hacker News checked. However, Paint does not receive updates through Windows Update. Consequently, organizations that rely on traditional patching workflows may leave the application unpatched.

Technical Details of the Microsoft Paint Vulnerability

CVE-2026-83844 is an out-of-bounds read vulnerability in Windows Paint. An attacker can exploit it by sending a specially crafted packet to an affected service over the network. The attack requires no sign-in and no user assistance. Microsoft has not named the specific affected service in its advisory.

Paint is installed separately for each user account on a PC. Windows can also keep a provisioned copy that it installs for each new user. Therefore, checking only the signed-in account may miss older copies. Administrators should inspect every user’s copy and the provisioned package to confirm the fix is present.

Microsoft’s security advisory originally listed 11.2605.91.0 as the fixed build. The advisory was later updated to name 11.2609.401.0 as the fixed build, but the revision history shows only the October 13 entry with no note about the change. The NVD entry still lists Paint as affected below 11.2605.91.0. A scanner that reads the CVE record may treat builds from 11.2605.91.0 up as fixed, even though the true fixed build is 11.2609.401.0.

Business and Operational Impact

  • Patch delivery gap: Because Paint updates through the Store and not Windows Update, organizations with locked-down Store policies or offline systems may not receive the fix automatically.
  • Scanner blind spots: Vulnerability scanners that rely on the NVD entry may report builds 11.2605.91.0 and above as fixed when they are not.
  • Multi-user oversight: Administrators who check only their own Paint copy may miss outdated versions under other user profiles or in the provisioned package.
  • Network exposure: The flaw can be exploited remotely over the network with no authentication, raising the risk for internet-facing or poorly segmented endpoints.

Mitigation and Recommendations

Immediate Actions for Defenders

  1. Run the following PowerShell commands as administrator to list every user’s copy of Paint and the provisioned copy:
Get-AppxPackage -AllUsers -Name Microsoft.Paint | Select-Object Version, @{ n = 'Users'; e = { $_.PackageUserInformation.UserSecurityId.Username -join ', ' } }
Get-AppxProvisionedPackage -Online | Where-Object DisplayName -eq 'Microsoft.Paint' | Select-Object Version
  1. Update Paint through the Microsoft Store, or allow Store auto-update to install the fixed build. In Intune and other device-management tools, trigger a Store app update scan across managed PCs.
  2. Re-run the commands and confirm every copy shows version 11.2609.401.0 or later.
  3. If Paint is not needed, remove it for every user and from the provisioned copy to eliminate the attack surface.

Verification and Monitoring

  • Treat Microsoft Store app updates as part of the patching lifecycle, not as optional consumer updates.
  • Audit Store update policies to ensure they are not blocked by firewall rules or device-management restrictions.
  • Review vulnerability scanner results for Paint and manually verify build numbers against the fixed version.

Bottom line: CVE-2026-83844 is a high-severity flaw in a default Windows app that bypasses traditional patching channels. Verify every copy of Paint on every PC, not just the one you are logged into.

Incident Summary

CVE ID / Incident: CVE-2026-83844
Affected Systems: Windows Paint (Microsoft Store app)
Disclosure Date: October 13, 2026
Patch Status: Fixed build 11.2609.401.0 available in Microsoft Store
CVSS Score: 8.1 (Important)
Exploitation Status: Not known to be exploited at time of disclosure

References

  1. Microsoft, “CVE-2026-83844 Security Update Guide,” October 13, 2026, https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-83844, accessed November 8, 2026.
  2. The Hacker News, “Microsoft Paint RCE Fix Now Available, but Windows Update Won’t Deliver It,” November 6, 2026, https://thehackernews.com/2026/11/microsoft-paint-rce-fix-now-available.html, accessed November 8, 2026.
  3. Brian Vitko, RFF, “Windows Paint CVE-2026-83844 Store Fix Missing,” https://getrff.com/blog/windows-paint-cve-2026-83844-store-fix-missing/, accessed November 8, 2026.
  4. National Vulnerability Database, “CVE-2026-83844 Detail,” https://nvd.nist.gov/vuln/detail/CVE-2026-83844, accessed November 8, 2026.

Tags:

CVEVulnerabilityWindows
Author

ogwatermelon

Follow Me
Other Articles
Previous

Claude Code Settings File Leaks 1,379 Secrets on GitHub

Next

CWPdoor Backdoor Hides Inside Control Web Panel Server, Evades Logs

AI Android Backdoor Botnet Breach CVE Exploit Hack Incident Infostealer KEV Linux Mac Malware Network News Phishing Ransomware RCE supp supply chain Virtualization Vishing Vulnerability Windows World Worm Zero Day

Meta

  • Log in
  • Entries feed
  • Comments feed
  • WordPress.org

Archives

  • November 2026
  • October 2026
  • September 2026
  • August 2026
  • July 2026
  • June 2026
  • May 2026

Categories

  • AI
  • Android
  • Apple
  • Backdoor
  • BotNet
  • Breach
  • CVE
  • exploit
  • Hack
  • Incident
  • Infostealer
  • KEV
  • Linux
  • Mac
  • Malware
  • News
  • Phishing
  • Ransomware
  • RCE
  • supply-chain
  • Uncategorized
  • Virtualization
  • Vishing
  • Vulnerability
  • Windows
  • World
  • Worm
  • Zero Day
Copyright 2026 — The Cybersecurity Focus. All rights reserved.