Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB
CVE-2026-91373 Overview
CVE-2026-91373 is a medium-severity vulnerability in the Java Secure Socket Extension (JSSE) component of Oracle Java SE. An unauthenticated remote attacker with network access via Transport Layer Security (TLS) can trigger a partial denial-of-service condition. The flaw maps to CWE-400, uncontrolled resource consumption. Oracle disclosed the issue in the October 2026 Critical Patch Update. Affected releases include Oracle Java SE 8u503, 8u503-perf, 11.0.32.1, 17.0.20.1, 21.0.12.1, and 25.0.4.1, Oracle GraalVM for JDK 17.0.20.1 and 21.0.12.1, and Oracle GraalVM Enterprise Edition 21.3.19.1.1.
Critical Impact
Remote unauthenticated attackers can degrade availability of Java-based TLS services and sandboxed Java Web Start or applet clients that process untrusted TLS data.
Affected Products
- Oracle Java SE: 8u503, 8u503-perf, 11.0.32.1, 17.0.20.1, 21.0.12.1, 25.0.4.1
- Oracle GraalVM for JDK: 17.0.20.1, 21.0.12.1
- Oracle GraalVM Enterprise Edition: 21.3.19.1.1
Discovery Timeline
- 2026-10-20 - CVE CVE-2026-91373 published to the National Vulnerability Database (NVD)
- 2026-10-22 - Last updated in NVD database
Technical Details for CVE-2026-91373
Vulnerability Analysis
The defect resides in JSSE, Java's TLS implementation. Attackers reach the vulnerable code path by initiating or participating in a TLS handshake or session with an affected Java runtime. Successful exploitation produces a partial denial of service by exhausting a bounded resource during protocol processing. Confidentiality and integrity are not affected. The issue is reachable through any API that consumes attacker-controlled TLS data, including web services, RPC endpoints, and TLS clients that connect to untrusted servers. Sandboxed Java Web Start applications and applets that handle untrusted code are also in scope.
Root Cause
Oracle classifies the weakness under CWE-400, uncontrolled resource consumption. The JSSE component fails to bound a resource during TLS processing, allowing a remote peer to force the Java Virtual Machine (JVM) to spend excessive CPU, memory, or thread capacity. Oracle has not published the specific internal function or protocol field responsible for the condition. See the Oracle October 2026 Critical Patch Update Advisory for vendor technical references.
Attack Vector
The attack vector is network. The attacker needs no authentication and no user interaction. A single TLS endpoint reachable by the attacker, either as a server exposed to the internet or as a client that connects outbound, is sufficient. Repeated malicious handshakes or sessions amplify the resource pressure and sustain the degraded state.
No verified proof-of-concept code is available. Refer to the Oracle October 2026 Security Alert for authoritative details.
Detection Methods for CVE-2026-91373
Indicators of Compromise
- Sustained spikes in CPU, heap, or thread usage on JVM processes that terminate TLS connections.
- Elevated rates of incomplete or abnormally slow TLS handshakes from a small set of source IP addresses.
- Repeated javax.net.ssl.SSLException or handshake timeout entries in application logs.
Detection Strategies
- Correlate JVM resource metrics with TLS handshake telemetry to identify hosts whose availability degrades during specific peer interactions.
- Monitor Java Flight Recorder or JMX metrics for anomalous allocation rates in sun.security.ssl classes.
- Baseline inbound TLS connection patterns and alert on sudden deviations in handshake duration or failure ratios.
Monitoring Recommendations
- Ingest application, web server, and reverse-proxy logs into a central analytics platform and alert on repeated TLS failures from the same source.
- Track JVM uptime, garbage collection pauses, and thread pool saturation across all Java workloads running affected versions.
- Enable network flow logging on TLS-exposed services to support post-incident attribution.
How to Mitigate CVE-2026-91373
Immediate Actions Required
- Inventory all Java Runtime Environment (JRE), Java Development Kit (JDK), and GraalVM installations and identify instances matching the affected versions.
- Apply the fixed releases from the Oracle October 2026 Critical Patch Update to every affected host and container image.
- Restrict exposure of Java-based TLS services to trusted networks until patching is complete.
Patch Information
Oracle addressed CVE-2026-91373 in the October 2026 Critical Patch Update. Administrators should install the updated Java SE, GraalVM for JDK, and GraalVM Enterprise Edition builds published in the Oracle October 2026 Security Alert. Rebuild container images that bundle the JRE or JDK and redeploy them across affected environments.
Workarounds
- Place rate limiting and connection quotas in front of TLS endpoints using a reverse proxy or load balancer to bound handshake volume per source.
- Terminate TLS at a patched proxy or offload engine so vulnerable JVMs do not process attacker-controlled handshake data directly.
- Enforce egress controls on Java clients to prevent connections to untrusted TLS servers that could trigger the condition.
# Verify installed Java version and plan upgrade
java -version
# Example: upgrade to a fixed Oracle Java SE release from the October 2026 CPU
# Replace the installer path with the patched build obtained from Oracle
sudo rpm -Uvh jdk-<fixed-version>_linux-x64_bin.rpm
java -version
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB

