CVE-2026-116540

Description

A flaw was found in netty-tcnative. A use-after-free vulnerability occurs during session ticket key rotation when handling concurrent connections. A remote attacker can exploit this flaw by initiating TLS (Transport Layer Security) handshakes while ticket keys are being rotated, causing the system to read previously freed memory. This issue can lead to corrupted ticket processing or an application crash, resulting in a Denial of Service (DoS).

Statement

This vulnerability is rated as Moderate impact because successful exploitation requires an attacker to win a precise timing race condition during session ticket key rotation, and the resulting blast radius is confined to a denial of service without compromising system confidentiality or integrity. In Red Hat environments, netty-tcnative provides native OpenSSL-backed cryptographic operations for enterprise Java integration frameworks. Exploitation requires the application to dynamically rotate TLS session ticket keys while simultaneously servicing incoming client handshakes, making unintended disruption or reliable exploitation unlikely in typical deployments.

Common Vulnerability Scoring System (CVSS) Score Details

Info alert:Important note

CVSS scores for open source components depend on vendor-specific factors (e.g. version or build chain). Therefore, Red Hat's score and impact rating can be different from NVD and other vendors. Red Hat remains the authoritative CVE Naming Authority (CNA) source for its products and services (see Red Hat classifications).

The following CVSS metrics and score provided are preliminary and subject to review.

CVSS v3 Score Breakdown

Red HatNVDcve.org
Base Score5.9N/A5.9
Attack VectorNetworkN/ANetwork
Attack ComplexityHighN/AHigh
Privileges RequiredNoneN/ANone
User InteractionNoneN/ANone
ScopeUnchangedN/AUnchanged
ConfidentialityNoneN/ANone
Integrity ImpactNoneN/ANone
Availability ImpactHighN/AHigh

Vector

Red Hat: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H

cve.org: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H

Understanding the Weakness (CWE)

Confidentiality

Technical Impact: Read Memory

If the expired pointer is used in a read operation, an attacker might be able to control data read in by the application.

Availability

Technical Impact: DoS: Crash, Exit, or Restart

If the expired pointer references a memory location that is not accessible to the product, or points to a location that is "malformed" (such as NULL) or larger than expected by a read or write operation, then a crash may occur.

Integrity,Confidentiality,Availability

Technical Impact: Execute Unauthorized Code or Commands

If the expired pointer is used in a function call, or points to unexpected data in a write operation, then code execution may be possible.

Frequently Asked Questions

Want to get errata notifications? Sign up here.