Netty Codec Mqtt
Approved changes feed: RSS · Atom
cpe:2.3:a:io.netty:netty-codec-mqtt:*:*:*:*:*:*:*:*
part: a version: * update: *
| Vendor | Io.Netty (7808cde2-d5c9-5fd6-931a-aabaf07399fd) |
|---|---|
| Product | Netty Codec Mqtt (1e20c34d-2484-580a-96e2-2c8e514477cf) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
| Notes | Imported from gcve-enriched-dumps CVE data |
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
| No PURL mappings for this CPE yet. | ||
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2026-44248 |
vulnerable | 2026-06-08 08:03:18.161941 |
Netty: Resource exhaustion in MqttDecoder
MEDIUM (5.3)
Netty is an asynchronous, event-driven network application framework. Prior to 4.2.13.Final and 4.1.133.Final, 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. This vulnerability is fixed in 4.2.13.Final and 4.1.133.Final.
Published: 2026-05-13T18:23:37.563Z
Updated: 2026-08-03T12:05:42.907Z |
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.