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-91379 Overview
CVE-2026-91379 is a use-after-free vulnerability [CWE-416] in the JDK tools component of Oracle Java SE, Oracle GraalVM for JDK, and Oracle GraalVM Enterprise Edition. The flaw lets an unauthenticated local attacker compromise integrity when a user runs untrusted sandboxed Java Web Start applications or sandboxed Java applets. Successful exploitation can allow unauthorized creation, deletion, or modification of data accessible to the Java runtime. The vulnerability does not affect server deployments that run only trusted administrator-installed code. Exploitation is difficult and requires user interaction.
Critical Impact
Attackers who convince a user to load untrusted sandboxed Java content can bypass sandbox integrity controls and modify data accessible to the Java runtime.
Affected Products
- Oracle Java SE: 8u503-perf, 11.0.32.1, 17.0.20.1, 21.0.12.1, 25.0.4.1, 27
- Oracle GraalVM for JDK: 17.0.20.1 and 21.0.12.1
- Oracle GraalVM Enterprise Edition: 21.3.19.1.1
Discovery Timeline
- 2026-10-20 - CVE CVE-2026-91379 published to NVD as part of the Oracle Critical Patch Update October 2026
- 2026-10-21 - Last updated in NVD database
Technical Details for CVE-2026-91379
Vulnerability Analysis
The vulnerability resides in JDK tools code shared across Oracle Java SE, Oracle GraalVM for JDK, and Oracle GraalVM Enterprise Edition. It is classified as a use-after-free condition [CWE-416], where memory is referenced after being released. In the context of the Java sandbox, this memory safety issue allows untrusted code to violate integrity boundaries that normally isolate sandboxed applets and Web Start applications from the host runtime.
The scope is limited to client deployments that load untrusted code from external sources and rely on the Java sandbox for isolation. Server deployments running only trusted code are not affected. Exploitation requires both local access to the system running the Java runtime and interaction from a user who executes the malicious sandboxed content.
Successful exploitation does not expose confidential data or impact availability, but allows unauthorized creation, deletion, or modification of data within the Java runtime's reach.
Root Cause
The root cause is a use-after-free condition in a JDK tools component. When an object is freed but a dangling reference remains reachable, subsequent operations against that reference produce undefined behavior that an attacker can shape through crafted inputs. Oracle has not published detailed technical specifics of the affected code path.
Attack Vector
An attacker delivers a crafted Java Web Start application or sandboxed applet that a victim loads on a system with a vulnerable Java runtime. The malicious code triggers the use-after-free during execution inside the sandbox, breaking the integrity boundary that the sandbox is designed to enforce. Attack complexity is high and user interaction is required.
No verified exploit code is publicly available. Refer to the Oracle Security Alert - October 2026 for vendor-supplied technical context.
Detection Methods for CVE-2026-91379
Indicators of Compromise
- Execution of javaws.exe or javaws loading JNLP files from untrusted or external network locations
- Java process crashes, memory faults, or unexpected child process spawning from java or javaw sessions tied to applet or Web Start content
- Unexpected file creation, deletion, or modification in user-writable directories by a Java process
- Browser or email client activity preceding Java runtime execution of remotely hosted .jnlp or applet payloads
Detection Strategies
- Inventory endpoints running affected Oracle Java SE and GraalVM versions and flag any invocation of Java Web Start or applet runtime components
- Correlate parent-child process relationships where browsers, mail clients, or document viewers spawn Java processes that then write to the filesystem
- Hunt for JNLP downloads over HTTP or HTTPS from non-corporate domains in web proxy and endpoint telemetry
Monitoring Recommendations
- Monitor command-line arguments passed to java, javaw, and javaws for references to remote JNLP URLs or untrusted class paths
- Alert on Java runtime access to sensitive user directories outside expected application behavior
- Track Java version coverage against the fixed releases listed in the Oracle October 2026 Critical Patch Update
How to Mitigate CVE-2026-91379
Immediate Actions Required
- Apply the Oracle Critical Patch Update October 2026 to all affected Oracle Java SE, Oracle GraalVM for JDK, and Oracle GraalVM Enterprise Edition installations
- Identify and remove unsupported Java client deployments that still permit Web Start or applet execution
- Enforce allowlists so that only approved internal JNLP sources can be loaded by Java Web Start
Patch Information
Oracle addressed CVE-2026-91379 in the October 2026 Critical Patch Update. Administrators should upgrade to the fixed releases listed in the Oracle Security Alert - October 2026. Server deployments that run only trusted code are not affected but should still be updated as part of routine patch cycles.
Workarounds
- Disable Java in web browsers on client systems that do not require applet execution
- Remove or restrict Java Web Start where business workflows do not depend on it
- Apply operating system execution controls to block launching JNLP files from untrusted locations
# Verify installed Java version against fixed releases
java -version
# Disable Java Web Start file association on Windows (example)
assoc .jnlp=
ftype JNLPFile=
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

