Live › vulnerability › CVE-2026-116541
Go to dashboardNetty's netty-tcnative library overreports bytes consumed in its TLS write callback, so queued post-handshake records such as NewSessionTicket or KeyUpdate can be mishandled. A remote TLS 1.3 peer can use this to truncate handshake flights, fail connections, or abort the JVM process.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-26 16:31 UTC. All times on this page are UTC.
Java services that terminate TLS through Netty with the netty-tcnative (BoringSSL-backed) provider and accept connections from remote peers are exposed. Services using only the JDK TLS provider, or no TLS listener, are not in the described path.
No product ranges from the sources yet.
2.0.84.Final.2.0.84.Final or later.Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
Netty netty-tcnative before 2.0.84.Final contains a denial of service vulnerability in the tcn_write_to_bytebuffer BIO write callback that overreports bytes consumed. Remote TLS 1.3 peers can provoke queued post-handshake records like NewSessionTicket or KeyUpdate to truncate flights, fail connections, or abort the JVM process.
This page as .md · .json · in your agent: get_signal("CVE-2026-116541")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.