CVE-2026-76816

published 24 Aug 2026 · updated 25 Aug 2026

Netty: MQTT Topic Name and Client ID Validation Bypass

3.5LowCVSS 3.5EPSS 0%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. No fixed version is recorded.

Netty is an asynchronous, event-driven network application framework. Prior to versions 4.1.137.Final and 4.2.17.Final, MqttEncoder does not validate client identifiers, will topics, usernames, and PUBLISH topic names before encoding, allowing prohibited null bytes in MQTT UTF-8 string fields and potentially causing routing, access-control, or identity mismatches in downstream brokers. The vulnerability is exploitable when an application uses Netty's MQTT encoder to construct messages from user-controlled input. This issue is fixed in versions 4.1.137.Final and 4.2.17.Final.

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
netty<4.1.137.Final, >=4.2.0.Final <4.1.137.Final

Timeline

Every event on this vulnerability

Embed

A live severity badge for an advisory, README or ticket

CVE-2026-76816 severity on Zeptric[![CVE-2026-76816](https://zeptric.io/badge/cve/CVE-2026-76816.svg)](https://zeptric.io/cve/CVE-2026-76816)