{"id":1009,"date":"2026-11-09T21:17:18","date_gmt":"2026-11-09T21:17:18","guid":{"rendered":"https:\/\/managedt.com\/blog\/microsoft-paint-rce-fix-store-updates\/"},"modified":"2026-11-11T00:19:32","modified_gmt":"2026-11-11T00:19:32","slug":"microsoft-paint-rce-fix-store-updates","status":"publish","type":"post","link":"https:\/\/managedt.com\/blog\/microsoft-paint-rce-fix-store-updates\/","title":{"rendered":"Microsoft Paint RCE Fix Available Through Store Updates"},"content":{"rendered":"<div class=\"post-updated\"><em>Updated November 10, 2026 at 7:16 PM ET<\/em><\/div>\n<p><a href=\"https:\/\/thehackernews.com\/2026\/11\/microsoft-paint-rce-fix-now-available.html\" target=\"_blank\" rel=\"noopener\">The source report<\/a> says the Microsoft Paint RCE fix is available through Microsoft Store updates, with build 11.2609.401.0 identified as fixed for CVE-2026-83844. Administrators should check each user copy and the provisioned copy because Paint is installed separately for each account, according to <a href=\"https:\/\/www.thehackernews.com\/2026\/11\/microsoft-paint-rce-fix-now-available-windows.html\" target=\"_blank\" rel=\"noopener\">the source report<\/a>.<\/p>\n<h2>What Happened<\/h2>\n<p><a href=\"https:\/\/thehackernews.com\/2026\/11\/microsoft-paint-rce-fix-now-available.html\" target=\"_blank\" rel=\"noopener\">The source report<\/a> says Microsoft made the Paint fix available through the Microsoft Store rather than Windows Update. Microsoft rates CVE-2026-83844 as Important with a CVSS score of 8.1, while public research published by HackingLZ describes the demonstrated defect as an out-of-bounds read in the legacy Paint C2PA\/JUMBF parser and says its evidence does not establish remote code execution.<\/p>\n<h2>Are You Affected?<\/h2>\n<p><a href=\"https:\/\/thehackernews.com\/2026\/11\/microsoft-paint-rce-fix-now-available.html\" target=\"_blank\" rel=\"noopener\">The source report<\/a> says Microsoft\u2019s security advisory identifies Paint build 11.2609.401.0 or later as fixed. It also says the CVE record still lists Paint versions below 11.2605.91.0 as affected, so a scanner that relies on that record may treat build 11.2605.91.0 or later as fixed even when a computer has not installed build 11.2609.401.0.<\/p>\n<p>Paint is installed separately for each user account. Windows can also retain a provisioned copy for installation on each new user account, which means a check of only the signed-in account can miss older copies. The source report states that the vulnerability was not known to be exploited or publicly disclosed when Microsoft published it on October 13, 2026, and that it was absent from the U.S. Cybersecurity and Infrastructure Security Agency\u2019s Known Exploited Vulnerabilities catalog when checked on November 6, 2026.<\/p>\n<h2>What to Do Now<\/h2>\n<ol>\n<li>Check each user\u2019s copy of Paint and the provisioned copy on each PC.<\/li>\n<li>Keep Paint installations updated through the Microsoft Store.<\/li>\n<li>Use your device-management tooling to check for and apply Store app updates across managed PCs.<\/li>\n<li>Recheck all copies after updating.<\/li>\n<\/ol>\n<h2>What Does the Latest Research Add?<\/h2>\n<p>The <a href=\"https:\/\/github.com\/HackingLZ\/CVE-2026-83844-public\/blob\/main\/README.md\" target=\"_blank\" rel=\"noopener\">HackingLZ research repository<\/a> provides a reproduction package for Paint builds below 11.2609.401.0 and describes the demonstrated behavior as \u201ca denial-of-service and limited local heap over-read primitive.\u201d The repository says the collected evidence does not establish remote code execution, adding technical detail to the earlier description of the flaw as an out-of-bounds read that could allow an attacker to run code over a network.<\/p>\n<p>The package identifies the legacy Paint C2PA\/JUMBF parser as the affected area. Its documented reproduction uses ARM64 Windows 11, Paint below build 11.2609.401.0, and an elevated interactive PowerShell session. The repository also includes a matched control image and evidence from direct testing, allowing the reported crash behavior to be examined alongside the affected build boundary.<\/p>\n<h2>Why Store-Only Delivery Matters for Managed Devices<\/h2>\n<p>Paint\u2019s per-user installation model requires a device-level remediation check. A computer can show a version that appears fixed in a scanner while another user copy or the provisioned package remains below the build Microsoft identifies as fixed.<\/p>\n<h2>FAQ<\/h2>\n<h3>Which Microsoft Paint Build Fixes CVE-2026-83844?<\/h3>\n<p><a href=\"https:\/\/thehackernews.com\/2026\/11\/microsoft-paint-rce-fix-now-available.html\" target=\"_blank\" rel=\"noopener\">The source report<\/a> says Microsoft\u2019s security advisory identifies build 11.2609.401.0 or later as fixed. It also says the CVE record lists versions below 11.2605.91.0 as affected.<\/p>\n<h3>Does Windows Update Install the Microsoft Paint Fix?<\/h3>\n<p>No. <a href=\"https:\/\/thehackernews.com\/2026\/11\/microsoft-paint-rce-fix-now-available.html\" target=\"_blank\" rel=\"noopener\">The source report<\/a> says the fix for CVE-2026-83844 is available through a Microsoft Store update to Paint.<\/p>\n<h3>How Should Administrators Check Every Paint Installation?<\/h3>\n<p>Review all user copies and the provisioned package, keep them updated through the Microsoft Store, and recheck them afterward.<\/p>\n<div class=\"source-disclaimer\"><em>This article reports on publicly available information from the sources listed below. We have no reason to believe it is inaccurate, but we have not independently verified every claim, and details may change as the story develops.<\/em><\/div>\n<section class=\"post-sources\">\n<h2>Sources<\/h2>\n<ul>\n<li><a href=\"https:\/\/thehackernews.com\/2026\/11\/microsoft-paint-rce-fix-now-available.html\" target=\"_blank\" rel=\"noopener nofollow\">Microsoft Paint RCE Fix Now Available, but Windows Update Won&#8217;t Deliver It, thehackernews.com, Nov 6, 2026<\/a><\/li>\n<li><a href=\"https:\/\/github.com\/HackingLZ\/CVE-2026-83844-public\/blob\/main\/README.md\" target=\"_blank\" rel=\"noopener nofollow\">github.com<\/a><\/li>\n<li><a href=\"https:\/\/learn.microsoft.com\/en-us\/answers\/questions\/6055591\/microsoft-paint-11-2605-91-0\" target=\"_blank\" rel=\"noopener nofollow\">learn.microsoft.com<\/a><\/li>\n<li><a href=\"https:\/\/techcommunity.microsoft.com\/blog\/azurenetworksecurityblog\/addressing-php2shell-cve-2026-109618-and-cve-2026-109619-upgrade-guidance-and-az\/4566623\" target=\"_blank\" rel=\"noopener nofollow\">techcommunity.microsoft.com<\/a><\/li>\n<li><a href=\"https:\/\/msrc.microsoft.com\/update-guide\/vulnerability\/CVE-2026-69370\" target=\"_blank\" rel=\"noopener nofollow\">msrc.microsoft.com<\/a><\/li>\n<\/ul>\n<\/section>\n<p><script type=\"application\/ld+json\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"FAQPage\",\"mainEntity\":[{\"@type\":\"Question\",\"name\":\"Which Microsoft Paint Build Fixes CVE-2026-83844?\",\"acceptedAnswer\":{\"@type\":\"Answer\",\"text\":\"The source report says Microsoft\u2019s security advisory identifies build 11.2609.401.0 or later as fixed. It also says the CVE record lists versions below 11.2605.91.0 as affected.\"}},{\"@type\":\"Question\",\"name\":\"Does Windows Update Install the Microsoft Paint Fix?\",\"acceptedAnswer\":{\"@type\":\"Answer\",\"text\":\"No. The source report says the fix for CVE-2026-83844 is available through a Microsoft Store update to Paint.\"}},{\"@type\":\"Question\",\"name\":\"How Should Administrators Check Every Paint Installation?\",\"acceptedAnswer\":{\"@type\":\"Answer\",\"text\":\"Review all user copies and the provisioned package, keep them updated through the Microsoft Store, and recheck them afterward.\"}}]}]}<\/script><\/p>\n","protected":false},"excerpt":{"rendered":"<p>Microsoft Paint build 11.2609.401.0 fixes CVE-2026-83844 through Microsoft Store, so administrators should check every user and provisioned copy.<\/p>\n","protected":false},"author":3,"featured_media":1008,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[],"class_list":["post-1009","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-uncategorized"],"_links":{"self":[{"href":"https:\/\/managedt.com\/blog\/wp-json\/wp\/v2\/posts\/1009","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/managedt.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/managedt.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"replies":[{"embeddable":true,"href":"https:\/\/managedt.com\/blog\/wp-json\/wp\/v2\/comments?post=1009"}],"version-history":[{"count":2,"href":"https:\/\/managedt.com\/blog\/wp-json\/wp\/v2\/posts\/1009\/revisions"}],"predecessor-version":[{"id":1020,"href":"https:\/\/managedt.com\/blog\/wp-json\/wp\/v2\/posts\/1009\/revisions\/1020"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/managedt.com\/blog\/wp-json\/wp\/v2\/media\/1008"}],"wp:attachment":[{"href":"https:\/\/managedt.com\/blog\/wp-json\/wp\/v2\/media?parent=1009"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/managedt.com\/blog\/wp-json\/wp\/v2\/categories?post=1009"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/managedt.com\/blog\/wp-json\/wp\/v2\/tags?post=1009"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}