Skip to content
Fencer Intel
medium 5.9

CVE-2026-116541 json

netty-tcnative before 2.0.84.Final Denial of Service via BIO Write Overcount

published 14d ago modified 14d ago also EUVD-2026-109911

cvss
5.9
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.5%
EPSS 0.5% chance of exploitation in 30 days, percentile 42%
public exploits
0
none known

Summary

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.

Patch / fix

  • netty netty-tcnative 2.0.84.Final
  • netty netty-tcnative-boringssl-static 2.0.84.Final
  • netty-tcnative openSUSE Tumbleweed 2.0.85-1.1

opensuse advisories openSUSE-SU-2026:12403-1

Is CVE-2026-116541 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2026-116541 updated cvss 5.9

io.netty/netty-tcnative: netty-tcnative: Denial of Service via write callback overreporting

  • Red Hat build of Apache Camel for Spring Boot 4 netty-tcnative 2.0.81.Final-redhat-00001
    affected: workaround, no fix available “Upgrade netty-tcnative to 2.0.84.Final or later; where upgrade is infeasible, disable the native transport (fall back to the JDK SSLEngine implementation) or restrict TLS 1.3 usage.”
  • Red Hat Fuse 7 netty-tcnative 2.0.81.Final-redhat-00001
    affected: workaround, no fix planned “Upgrade netty-tcnative to 2.0.84.Final or later; where upgrade is infeasible, disable the native transport (fall back to the JDK SSLEngine implementation) or restrict TLS 1.3 usage.”

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
partial
Assessed
14d ago

Exploit prediction

0.49% chance of exploitation in the next 30 days, higher than 42% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
CNA 4.0 8.2 CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N
CNA 3.1 5.9 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H
CNA 4.0 8.2 CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

Affected products

  • netty netty-tcnative
  • netty netty-tcnative-boringssl-static

Classification

Weakness

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.