<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Rce on born0monday</title>
    <link>https://born0monday.me/tags/rce/</link>
    <description>Recent content in Rce on born0monday</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Wed, 04 Nov 2026 08:00:00 +0100</lastBuildDate>
    <atom:link href="https://born0monday.me/tags/rce/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Pwning Home Assistant Green: Pre-Auth RCE in Eclipse Mosquitto</title>
      <link>https://born0monday.me/posts/ha-green-mosquitto-rce/</link>
      <pubDate>Wed, 04 Nov 2026 00:00:00 +0000</pubDate>
      <guid>https://born0monday.me/posts/ha-green-mosquitto-rce/</guid>
      <description>&lt;p&gt;In this writeup I&amp;rsquo;m going to demonstrate that a seemingly benign bug in Eclipse Mosquitto, publicly disclosed back in August 2026 and still unpatched upstream, can in fact be exploited to gain unauthenticated (pre-auth) RCE. The GitHub issue&lt;sup id=&#34;fnref:1&#34;&gt;&lt;a href=&#34;#fn:1&#34; class=&#34;footnote-ref&#34; role=&#34;doc-noteref&#34;&gt;1&lt;/a&gt;&lt;/sup&gt; incorrectly concluded that the bug has no impact on memory safety. I had found the flaw independently about a week earlier while researching the Home Assistant Green for Pwn2Own Ireland 2026&lt;sup id=&#34;fnref:2&#34;&gt;&lt;a href=&#34;#fn:2&#34; class=&#34;footnote-ref&#34; role=&#34;doc-noteref&#34;&gt;2&lt;/a&gt;&lt;/sup&gt;, but the public disclosure made it ineligible for the competition. This writeup also includes advisory information for affected users. See the Affected section below.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
