<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://db.gcve.eu</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Tue, 06 Oct 2026 03:25:17 +0000</lastBuildDate>
    <item>
      <title>GHSA-jfg9-48mv-9qgx — Netty MQTT: Resource exhaustion in MqttDecoder</title>
      <link>https://db.gcve.eu/vuln/ghsa-jfg9-48mv-9qgx</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Maven: io.netty:netty-codec-mqtt&lt;/p&gt;
&lt;p&gt;### Impact
The MQTT 5 header Properties section is parsed and buffered _before_ any message size limit is applied.&lt;/p&gt;
&lt;p&gt;Specifically, in `MqttDecoder`, the `decodeVariableHeader()` method is called before the `bytesRemainingBeforeVariableHeader &amp;gt; maxBytesInMessage` check. The `decodeVariableHeader()` can call other methods which will call `decodeProperties()`. Effectively, Netty does not apply any limits to the size of the properties being decoded.&lt;/p&gt;
&lt;p&gt;Additionally, because `MqttDecoder` extends `ReplayingDecoder`, Netty will repeatedly re-parse the enormous Properties sections and buffer the bytes in memory, until the entire thing parses to completion.&lt;/p&gt;
&lt;p&gt;This can cause high resource usage in both CPU and memory.&lt;/p&gt;
&lt;p&gt;### Resources
`ANT-2026-09608`
https://docs.oasis-open.org/mqtt/mqtt/v5.0/os/mqtt-v5.0-os.html#_Toc3901027&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Maven: io.netty:netty-codec-mqtt&lt;/p&gt;
&lt;p&gt;### Impact
The MQTT 5 header Properties section is parsed and buffered _before_ any message size limit is applied.&lt;/p&gt;
&lt;p&gt;Specifically, in `MqttDecoder`, the `decodeVariableHeader()` method is called before the `bytesRemainingBeforeVariableHeader &amp;gt; maxBytesInMessage` check. The `decodeVariableHeader()` can call other methods which will call `decodeProperties()`. Effectively, Netty does not apply any limits to the size of the properties being decoded.&lt;/p&gt;
&lt;p&gt;Additionally, because `MqttDecoder` extends `ReplayingDecoder`, Netty will repeatedly re-parse the enormous Properties sections and buffer the bytes in memory, until the entire thing parses to completion.&lt;/p&gt;
&lt;p&gt;This can cause high resource usage in both CPU and memory.&lt;/p&gt;
&lt;p&gt;### Resources
`ANT-2026-09608`
https://docs.oasis-open.org/mqtt/mqtt/v5.0/os/mqtt-v5.0-os.html#_Toc3901027&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/ghsa-jfg9-48mv-9qgx</guid>
    </item>
  </channel>
</rss>
