CVE-2026-116542: Netty netty-tcnative before 2.0.84.Final SNI Hostname Spoofing via Modified UTF-8 Decoding
netty · netty-tcnative
Fixed in 2.0.84.Final · Affected: netty-tcnative before 2.0.84.Final · Exploitation: unlikely (under 1%)
Not in CyberSIXT coverage yet: no article names this CVE. This page shows the public record.
Higher than 11% of scored CVEs
DescriptionCVE.org
Netty netty-tcnative before 2.0.84.Final contains an SNI hostname spoofing vulnerability that allows remote unauthenticated clients to alter hostnames via JNI NewStringUTF decoding. Attackers can send overlong encodings like 0xC0 0x80 in the ClientHello server_name to confuse SNI-based certificate selection, access decisions, and logging.
Affected products2
From the CVE record. A product or version that is not listed is unknown, not unaffected.
- netty · netty-tcnativebefore 2.0.84.Final
- netty · netty-tcnative-boringssl-staticbefore 2.0.84.Final
On the Atlas
Every published CVE is on the CyberSIXT Atlas, grouped by weakness, vendor and month.
- Exploitation
- Unlikely (under 1%). EPSS under 1%, or no score yet.
- CISA KEV
- Not listed
- Public check
- No public nuclei template
- Vendor
- netty
- Published
- October 2026
CoverageNo articles yet
No CyberSIXT article names CVE-2026-116542 yet, so there is no coverage timeline, action brief or change log for it. Everything on this page comes from the public CVE record, CISA KEV, EPSS and the nuclei template index. Search the archive or see the CVEs in the news.