CVE-2026-116542
Published:October 26, 2026
Updated:October 28, 2026
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 Packages
https://github.com/netty/netty-tcnative.git (GITHUB):
Affected version(s) >=netty-tcnative-parent-2.0.1.Final <netty-tcnative-parent-2.0.84.FinalFix Suggestion:
Update to version netty-tcnative-parent-2.0.84.Finalio.netty:netty-tcnative (JAVA):
Affected version(s) >=2.0.1.Final <2.0.84.FinalFix Suggestion:
Update to version 2.0.84.Finalio.netty:netty-tcnative-boringssl-static (JAVA):
Affected version(s) >=2.0.1.Final <2.0.84.FinalFix Suggestion:
Update to version 2.0.84.FinalRelated Resources (7)
Do you need more information?
Contact UsCVSS v4
Base Score:
6.9
Attack Vector
NETWORK
Attack Complexity
LOW
Attack Requirements
NONE
Privileges Required
NONE
User Interaction
NONE
Vulnerable System Confidentiality
NONE
Vulnerable System Integrity
LOW
Vulnerable System Availability
NONE
Subsequent System Confidentiality
NONE
Subsequent System Integrity
NONE
Subsequent System Availability
NONE
CVSS v3
Base Score:
5.3
Attack Vector
NETWORK
Attack Complexity
LOW
Privileges Required
NONE
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
NONE
Integrity
LOW
Availability
NONE
Weakness Type (CWE)
Improper Handling of Unicode Encoding