All reports
Medium

Netty MQTT: Resource exhaustion in MqttDecoder

Affected versions

Affected versions
<= 4.1.132.Final
Fixed version
4.1.133.Final
Affected versions
>= 4.2.0.Alpha1, <= 4.2.12.Final
Fixed version
4.2.13.Final
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported

Exploitation

CVE-2026-44248

Probability of exploitation in the next 30 days: 0.56%

FIRST EPSS · 2026-11-18

Description

Impact

The MQTT 5 header Properties section is parsed and buffered before any message size limit is applied.

Specifically, in MqttDecoder, the decodeVariableHeader() method is called before the bytesRemainingBeforeVariableHeader > 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.

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.

This can cause high resource usage in both CPU and memory.

Resources

ANT-2026-09608 https://docs.oasis-open.org/mqtt/mqtt/v5.0/os/mqtt-v5.0-os.html#_Toc3901027

Links

Credits

  • chrisvest