Netty tcnative/tcnative-boringssl-static up to 2.0.83 BIO Write Callback tcn_write_to_bytebuffer denial of service

Summaryinfo

A vulnerability identified as problematic has been detected in Netty tcnative and tcnative-boringssl-static up to 2.0.83. This affects the function tcn_write_to_bytebuffer of the component BIO Write Callback. This manipulation causes denial of service. This vulnerability is registered as CVE-2026-116541. Remote exploitation of the attack is possible. No exploit is available. You should upgrade the affected component.

Detailsinfo

A vulnerability has been found in Netty tcnative and tcnative-boringssl-static up to 2.0.83 and classified as problematic. Affected by this vulnerability is the function tcn_write_to_bytebuffer of the component BIO Write Callback. The manipulation with an unknown input leads to a denial of service vulnerability. The CWE definition for the vulnerability is CWE-404. The product does not release or incorrectly releases a resource before it is made available for re-use. As an impact it is known to affect availability. The summary by CVE is:

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.

The advisory is shared at github.com. This vulnerability is known as CVE-2026-116541 since 10/26/2026. The exploitation appears to be easy. The attack can be launched remotely. The exploitation doesn't need any form of authentication. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1499 for this issue.

Upgrading to version 2.0.84.Final eliminates this vulnerability.

The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2026-109911). Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Productinfo

Vendor

• Netty

Name

• tcnative
• tcnative-boringssl-static

Version

• 2.0.0
• 2.0.1
• 2.0.2
• 2.0.3
• 2.0.4
• 2.0.5
• 2.0.6
• 2.0.7
• 2.0.8
• 2.0.9
• 2.0.10
• 2.0.11
• 2.0.12
• 2.0.13
• 2.0.14
• 2.0.15
• 2.0.16
• 2.0.17
• 2.0.18
• 2.0.19
• 2.0.20
• 2.0.21
• 2.0.22
• 2.0.23
• 2.0.24
• 2.0.25
• 2.0.26
• 2.0.27
• 2.0.28
• 2.0.29
• 2.0.30
• 2.0.31
• 2.0.32
• 2.0.33
• 2.0.34
• 2.0.35
• 2.0.36
• 2.0.37
• 2.0.38
• 2.0.39
• 2.0.40
• 2.0.41
• 2.0.42
• 2.0.43
• 2.0.44
• 2.0.45
• 2.0.46
• 2.0.47
• 2.0.48
• 2.0.49
• 2.0.50
• 2.0.51
• 2.0.52
• 2.0.53
• 2.0.54
• 2.0.55
• 2.0.56
• 2.0.57
• 2.0.58
• 2.0.59
• 2.0.60
• 2.0.61
• 2.0.62
• 2.0.63
• 2.0.64
• 2.0.65
• 2.0.66
• 2.0.67
• 2.0.68
• 2.0.69
• 2.0.70
• 2.0.71
• 2.0.72
• 2.0.73
• 2.0.74
• 2.0.75
• 2.0.76
• 2.0.77
• 2.0.78
• 2.0.79
• 2.0.80
• 2.0.81
• 2.0.82
• 2.0.83

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Discussion