Debian Package Tracker
Register | Log in
Subscribe

netty-tcnative

Choose email to subscribe with

general
  • source: netty-tcnative (main)
  • version: 2.0.85-1
  • maintainer: Debian Java Maintainers (archive) (DMD)
  • uploaders: Emmanuel Bourg (DMD)
  • arch: all any
  • std-ver: 4.7.4
  • VCS: Git (Browse, QA)
versions [more versions can be listed by madison] [old versions available from snapshot.debian.org]
[pool directory]
  • o-o-stable: 2.0.28-1
  • oldstable: 2.0.28-1
  • stable: 2.0.28-1
  • testing: 2.0.28-1
  • unstable: 2.0.85-1
versioned links
  • 2.0.28-1: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
  • 2.0.85-1: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
binaries
  • libnetty-tcnative-java
  • libnetty-tcnative-jni
action needed
4 security issues in trixie high

There are 4 open security issues in trixie.

4 important issues:
  • CVE-2026-116539: Netty netty-tcnative before 2.0.84.Final contains a heap buffer overflow vulnerability in the tcn_write_to_bytebuffer BIO callback caused by failing to wrap the non-application ring buffer write index. Remote TLS peers can drive handshake, renegotiation, or post-handshake messages into this buffer, triggering an out-of-bounds memcpy that crashes the JVM process.
  • CVE-2026-116540: netty-tcnative 2.0.66.Final before 2.0.84.Final built against OpenSSL 3.x contains a use-after-free vulnerability in ssl_tlsext_ticket_key_cb during session ticket key rotation. Remote clients performing TLS handshakes while setSessionTicketKeys0 frees the shared key array cause OpenSSL to read freed HMAC keys, crashing or corrupting ticket processing.
  • CVE-2026-116541: 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.
  • CVE-2026-116542: 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.
Created: 2026-10-27 Last update: 2026-11-16 17:30
4 security issues in forky high

There are 4 open security issues in forky.

4 important issues:
  • CVE-2026-116539: Netty netty-tcnative before 2.0.84.Final contains a heap buffer overflow vulnerability in the tcn_write_to_bytebuffer BIO callback caused by failing to wrap the non-application ring buffer write index. Remote TLS peers can drive handshake, renegotiation, or post-handshake messages into this buffer, triggering an out-of-bounds memcpy that crashes the JVM process.
  • CVE-2026-116540: netty-tcnative 2.0.66.Final before 2.0.84.Final built against OpenSSL 3.x contains a use-after-free vulnerability in ssl_tlsext_ticket_key_cb during session ticket key rotation. Remote clients performing TLS handshakes while setSessionTicketKeys0 frees the shared key array cause OpenSSL to read freed HMAC keys, crashing or corrupting ticket processing.
  • CVE-2026-116541: 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.
  • CVE-2026-116542: 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.
Created: 2026-10-27 Last update: 2026-11-16 17:30
4 security issues in bookworm high

There are 4 open security issues in bookworm.

4 important issues:
  • CVE-2026-116539: Netty netty-tcnative before 2.0.84.Final contains a heap buffer overflow vulnerability in the tcn_write_to_bytebuffer BIO callback caused by failing to wrap the non-application ring buffer write index. Remote TLS peers can drive handshake, renegotiation, or post-handshake messages into this buffer, triggering an out-of-bounds memcpy that crashes the JVM process.
  • CVE-2026-116540: netty-tcnative 2.0.66.Final before 2.0.84.Final built against OpenSSL 3.x contains a use-after-free vulnerability in ssl_tlsext_ticket_key_cb during session ticket key rotation. Remote clients performing TLS handshakes while setSessionTicketKeys0 frees the shared key array cause OpenSSL to read freed HMAC keys, crashing or corrupting ticket processing.
  • CVE-2026-116541: 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.
  • CVE-2026-116542: 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.
Created: 2026-10-27 Last update: 2026-11-16 17:30
testing migrations
  • This package will soon be part of the auto-openssl transition. You might want to ensure that your package is ready for it. You can probably find supplementary information in the debian-release archives or in the corresponding release.debian.org bug.
  • excuses:
    • Migrates after: netty-jni-util
    • Migration status for netty-tcnative (2.0.28-1 to 2.0.85-1): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
    • Issues preventing migration:
    • ∙ ∙ Missing build on armhf
    • ∙ ∙ Missing build on riscv64
    • ∙ ∙ Autopkgtest deferred on armhf: missing arch:armhf build
    • ∙ ∙ Autopkgtest deferred on riscv64: missing arch:riscv64 build
    • ∙ ∙ Lintian check waiting for test results - info
    • ∙ ∙ Reproducibility check waiting for results on amd64 - info
    • ∙ ∙ Reproducibility check deferred on armhf: missing builds - info
    • ∙ ∙ Reproducibility check waiting for results on i386 - info
    • ∙ ∙ Too young, only 1 of 5 days old
    • ∙ ∙ Build-Depends(-Arch): netty-tcnative netty-jni-util
    • Additional info (not blocking):
    • ∙ ∙ Piuparts tested OK - https://piuparts.debian.org/sid/source/n/netty-tcnative.html
    • ∙ ∙ Reproduced on arm64 - info
    • Not considered
news
[rss feed]
  • [2026-11-16] Accepted netty-tcnative 2.0.85-1 (source) into unstable (Emmanuel Bourg)
  • [2020-02-29] netty-tcnative 2.0.28-1 MIGRATED to testing (Debian testing watch)
  • [2020-02-24] Accepted netty-tcnative 2.0.28-1 (source) into unstable (Emmanuel Bourg)
  • [2019-01-27] netty-tcnative 2.0.20-1 MIGRATED to testing (Debian testing watch)
  • [2019-01-22] Accepted netty-tcnative 2.0.20-1 (source) into unstable (Emmanuel Bourg)
  • [2018-09-09] netty-tcnative 2.0.15-2 MIGRATED to testing (Debian testing watch)
  • [2018-09-03] Accepted netty-tcnative 2.0.15-2 (source) into unstable (Emmanuel Bourg)
  • [2018-09-03] Accepted netty-tcnative 2.0.15-1 (source) into unstable (Emmanuel Bourg)
  • [2017-02-03] netty-tcnative 1.1.33.Fork26-1 MIGRATED to testing (Debian testing watch)
  • [2017-01-23] Accepted netty-tcnative 1.1.33.Fork26-1 (source all amd64) into unstable (Emmanuel Bourg)
  • [2017-01-16] netty-tcnative 1.1.33.Fork25-1 MIGRATED to testing (Debian testing watch)
  • [2017-01-06] Accepted netty-tcnative 1.1.33.Fork25-1 (source all amd64) into unstable (Emmanuel Bourg)
  • [2016-12-26] netty-tcnative 1.1.33.Fork24-1 MIGRATED to testing (Debian testing watch)
  • [2016-12-15] Accepted netty-tcnative 1.1.33.Fork24-1 (source all amd64) into unstable (Emmanuel Bourg)
  • [2016-11-21] netty-tcnative 1.1.33.Fork23-2 MIGRATED to testing (Debian testing watch)
  • [2016-11-15] Accepted netty-tcnative 1.1.33.Fork23-2 (source all amd64) into unstable (Emmanuel Bourg)
  • [2016-10-09] netty-tcnative 1.1.33.Fork23-1 MIGRATED to testing (Debian testing watch)
  • [2016-10-03] Accepted netty-tcnative 1.1.33.Fork23-1 (source all amd64) into unstable (Emmanuel Bourg)
  • [2016-09-25] netty-tcnative 1.1.33.Fork22-1 MIGRATED to testing (Debian testing watch)
  • [2016-09-19] Accepted netty-tcnative 1.1.33.Fork22-1 (source all amd64) into unstable (Emmanuel Bourg)
  • [2016-09-04] netty-tcnative 1.1.33.Fork21-1 MIGRATED to testing (Debian testing watch)
  • [2016-08-29] Accepted netty-tcnative 1.1.33.Fork21-1 (source all amd64) into unstable (Emmanuel Bourg)
  • [2016-07-22] netty-tcnative 1.1.33.Fork19-1 MIGRATED to testing (Debian testing watch)
  • [2016-07-16] Accepted netty-tcnative 1.1.33.Fork19-1 (source all amd64) into unstable (Emmanuel Bourg)
  • [2016-04-02] netty-tcnative 1.1.33.Fork15-1 MIGRATED to testing (Debian testing watch)
  • [2016-03-27] Accepted netty-tcnative 1.1.33.Fork15-1 (source all amd64) into unstable (Emmanuel Bourg)
  • [2016-03-01] netty-tcnative 1.1.33.Fork14-1 MIGRATED to testing (Debian testing watch)
  • [2016-02-25] Accepted netty-tcnative 1.1.33.Fork14-1 (source all amd64) into unstable (Emmanuel Bourg)
  • [2016-02-04] Accepted netty-tcnative 1.1.33.Fork12-1 (source all amd64) into unstable (Emmanuel Bourg)
  • [2016-01-31] Accepted netty-tcnative 1.1.33.Fork11-1 (source all amd64) into unstable (Emmanuel Bourg)
  • 1
  • 2
bugs [bug history graph]
  • all: 0
links
  • homepage
  • buildd: logs, reproducibility, cross
  • popcon
  • browse source code
  • other distros
  • security tracker
  • debian patches
ubuntu Ubuntu logo [Information about Ubuntu for Debian Developers]
  • version: 2.0.28-1build6

Debian Package Tracker — Copyright 2013-2025 The Distro Tracker Developers
Report problems to the tracker.debian.org pseudo-package in the Debian BTS.
Documentation — Bugs — Git Repository — Contributing