CVE-2026-86243

Description

A flaw was found in Apache Tomcat Native. A remote attacker can exploit a buffer over-read vulnerability during the Transport Layer Security (TLS) handshake. Successful exploitation causes the Java Virtual Machine (JVM) to crash, resulting in a denial of service (DoS).

Statement

Red Hat rates this flaw as Important. An unauthenticated remote attacker can trigger a denial of service by exploiting a buffer over-read in Apache Tomcat Native during the TLS handshake, causing the JVM to crash. The issue affects deployments using vulnerable Tomcat Native versions.

Mitigation

Upgrade Apache Tomcat Native to version 1.3.9 or 2.0.16, as appropriate for the version line. For Red Hat JBoss Web Server, apply the corresponding Red Hat update for the affected stream when available. The Apache advisory does not specify an alternate workaround.

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).

CVSS v3 Score Breakdown

Red HatNVDcve.org
Base Score7.5N/A7.5
Attack VectorNetworkN/ANetwork
Attack ComplexityLowN/ALow
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:L/PR:N/UI:N/S:U/C:N/I:N/A:H

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

Understanding the Weakness (CWE)

Confidentiality

Technical Impact: Read Memory

Confidentiality

Technical Impact: Bypass Protection Mechanism

By reading out-of-bounds memory, an attacker might be able to get secret values, such as memory addresses, which can bypass protection mechanisms such as ASLR in order to improve the reliability and likelihood of exploiting a separate weakness to achieve code execution instead of just denial of service.

Availability,Integrity

Technical Impact: DoS: Crash, Exit, or Restart

An attacker might be able to cause a crash or other denial of service by causing the product to read a memory location that is not allowed (such as a segmentation fault), or to cause other conditions in which the read operation returns more data than is expected.

Frequently Asked Questions

Want to get errata notifications? Sign up here.