CVE-2026-70907
Description
A flaw was found in OpenJDK. An unauthenticated remote attacker can cause a Denial of Service (DoS) by repeatedly sending replayed handshake initiation messages (ClientHello) to a Transport Layer Security (TLS) server. Because the server fails to properly restrict the negotiation loop, it emits an unbounded number of retry requests (HelloRetryRequest), consuming server resources.
Statement
This flaw is assessed as having a Moderate impact because an unauthenticated remote attacker can cause resource exhaustion, but cannot execute arbitrary code, escalate privileges, or compromise confidential data. In Red Hat environments, exposure is limited to server applications running on OpenJDK that directly accept and terminate TLS 1.3 connections. Deployments fronted by reverse proxies or load balancers that handle TLS termination beforehand, as well as Java client applications, are not affected.
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 Hat | NVD | cve.org | |
|---|---|---|---|
| Base Score | 5.3 | N/A | 5.3 |
| Attack Vector | Network | N/A | Network |
| Attack Complexity | Low | N/A | Low |
| Privileges Required | None | N/A | None |
| User Interaction | None | N/A | None |
| Scope | Unchanged | N/A | Unchanged |
| Confidentiality | None | N/A | None |
| Integrity Impact | None | N/A | None |
| Availability Impact | Low | N/A | Low |
Vector
Red Hat: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
cve.org: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
Understanding the Weakness (CWE)
Availability
Technical Impact: DoS: Resource Consumption (CPU); DoS: Resource Consumption (Memory); DoS: Resource Consumption (Other)
When allocating resources without limits, an attacker could prevent other systems, applications, or processes from accessing the same type of resource. It can be easy for an attacker to consume many resources by rapidly making many requests or causing larger resources to be used than is needed.
Frequently Asked Questions
Not sure what something means? Check out our Security Glossary.
Want to get errata notifications? Sign up here.