<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Patch Gap on HackingPassion.com : root@HackingPassion.com-[~]</title><link>https://hackingpassion.com/tags/patch-gap/</link><description>Recent content in Patch Gap on HackingPassion.com : root@HackingPassion.com-[~]</description><generator>Hugo</generator><language>en</language><lastBuildDate>Thu, 10 Sep 2026 14:38:21 +0200</lastBuildDate><atom:link href="https://hackingpassion.com/tags/patch-gap/index.xml" rel="self" type="application/rss+xml"/><item><title>BlueMoon Chained Two Chrome Bugs to a Windows Flaw While the Fix Sat in Public for 27 Days</title><link>https://hackingpassion.com/bluemoon-chrome-windows-exploit-chain/</link><pubDate>Thu, 10 Sep 2026 14:38:21 +0200</pubDate><guid>https://hackingpassion.com/bluemoon-chrome-windows-exploit-chain/</guid><description>&lt;p>&lt;strong>Five spy crews broke into Chrome with the same kit in seven days.&lt;/strong> The victims clicked one link in an email. Google fixed the first hole on &lt;strong>August 7&lt;/strong>. It reached your browser on &lt;strong>September 3&lt;/strong>.&lt;/p>
&lt;p>The mail looked normal. The link looked normal. You clicked, a page started loading, and it sat there for a few seconds. Then it dropped you at &lt;code>github.com&lt;/code>, a site you know. The browser never said a word. &lt;strong>By then somebody else was already running code on your machine.&lt;/strong>&lt;/p></description></item></channel></rss>