<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Microsoft Paint on HackingPassion.com : root@HackingPassion.com-[~]</title><link>https://hackingpassion.com/tags/microsoft-paint/</link><description>Recent content in Microsoft Paint on HackingPassion.com : root@HackingPassion.com-[~]</description><generator>Hugo</generator><language>en</language><lastBuildDate>Tue, 10 Nov 2026 11:43:51 +0100</lastBuildDate><atom:link href="https://hackingpassion.com/tags/microsoft-paint/index.xml" rel="self" type="application/rss+xml"/><item><title>Windows Paint Had a Code Execution Hole and the Fix Microsoft Named Never Reached the Store</title><link>https://hackingpassion.com/windows-paint-fix-store-update/</link><pubDate>Tue, 10 Nov 2026 11:43:51 +0100</pubDate><guid>https://hackingpassion.com/windows-paint-fix-store-update/</guid><description>&lt;p>&lt;strong>One crafted file opened in Paint could run an attacker&amp;rsquo;s code.&lt;/strong> In all 6 countries checked, the Store had no safe Paint. Auto-updates did not help. The fix Microsoft named on October 13 never got there.&lt;/p>
&lt;p>On November 5, a Windows 11 PC with automatic app updates switched on in the Microsoft Store showed no update for Paint. Its owner assumed Paint was fine, and then looked up the version in the app&amp;rsquo;s settings.&lt;/p></description></item></channel></rss>