MS Paint Remote Code Execution Vulnerability

A newly disclosed high‑severity vulnerability (CVE‑2026‑83844) in the Windows 11 version of Microsoft Paint allows remote code execution, with Microsoft’s advisory claiming it can be exploited over the network without any user interaction. Commenters question how an ostensibly simple, offline image editor could be remotely reachable at all, speculating about interactions with Copilot, image parsing, or other Windows services, and some suspect Microsoft reused generic boilerplate language in the CVE description. The incident fuels broader frustration over feature creep, AI integration, and networked “telemetry” in formerly minimal desktop utilities, while practical advice centers on updating Paint via the Microsoft Store or removing it entirely in hardened environments.

Nature of the vulnerability

  • CVE-2026-83844 is a remote code execution (RCE) in Windows 11 Paint, described as an out-of-bounds read leading to code execution.
  • Official scoring: high severity (CVSS 8.1), vector AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H.
  • Microsoft states no authentication or user interaction is required, and describes it as exploitable via a “specially crafted packet” to a “network-bound” component.

Network vs. local/file-based attack (major confusion)

  • Many commenters question how Paint could be “network-bound,” since it has no obvious network-facing server or open port.
  • Several suspect boilerplate text was copy-pasted from other wormable CVEs and may misrepresent the real vector.
  • Other hypotheses (all speculative in the thread):
    • Some service or OS component might call Paint in response to remote input (e.g., file shares, thumbnailing, indexing).
    • Copilot/AI, telemetry, or update-check features might involve outbound connections that are MITM‑able.
  • Overall, the actual exploit path is widely viewed as unclear or possibly misdescribed.

Scope and affected versions

  • Affects “modern” Windows 11 Paint (Store app) from 11.0.0.0 up to but not including 11.2605.91.0.
  • Older “classic” mspaint.exe on earlier Windows appears unaffected per thread interpretation, though some note all image parsers are inherently risky.
  • One comment notes fix version as 11.2609.401.0; there is confusion over whether different Microsoft sources agree on the exact fixed build.

Patching and distribution

  • Paint updates come via Microsoft Store, not standard Windows Update, surprising some users.
  • Users report needing to manually open the Store’s Paint page to trigger the update; firewall-blocked Store traffic complicates patching.

Reactions to Paint’s evolution and AI features

  • Strong nostalgia for a simple, offline Paint; frustration that it now has layers, AI, and possibly network code.
  • Some see this as emblematic of “feature creep” and the drive to inject AI into everything.
  • A few suggest uninstalling or “86-ing” Paint entirely on managed systems.

Broader security and industry commentary

  • Thread ties this to a pattern of vulnerabilities in trivial or “toy” apps (Notepad, Minesweeper jokes, etc.).
  • Mixed views: some argue this reflects longstanding unsafe languages/legacy code; others note serious bugs also exist in “elite” modern code.
  • Several comments express renewed interest in minimal or air‑gapped setups and skepticism toward telemetry-heavy software.