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-91397 Overview
CVE-2026-91397 is a vulnerability in the Serviceability component of Oracle Java SE, Oracle GraalVM for JDK, and Oracle GraalVM Enterprise Edition. The flaw allows an unauthenticated attacker with local access to the infrastructure running the affected Java runtime to compromise integrity and availability. Exploitation is difficult and requires user interaction from a victim other than the attacker.
Successful exploitation enables unauthorized update, insert, or delete access to a subset of accessible data and can cause a partial denial of service. The vulnerability also affects sandboxed Java Web Start applications and sandboxed Java applets that execute untrusted code relying on the Java sandbox for security.
Critical Impact
Attackers can tamper with a subset of Java runtime data and trigger partial denial of service in affected Oracle Java SE and GraalVM deployments, including sandboxed client-side Java workloads.
Affected Products
- Oracle Java SE: 8u503, 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-91397 published to NVD as part of the Oracle Critical Patch Update
- 2026-10-21 - Last updated in NVD database
Technical Details for CVE-2026-91397
Vulnerability Analysis
The vulnerability resides in the Serviceability component of the Java runtime, which provides interfaces for monitoring, debugging, and diagnostics of running Java applications. The flaw permits an attacker who can log on to the local infrastructure, in combination with victim interaction, to alter a limited scope of runtime data and partially disrupt availability.
The attack path requires difficult preconditions. The attacker needs local logon access and must induce a separate user to perform an action, such as running a crafted Java application or loading content that invokes the vulnerable Serviceability APIs. Despite the narrow conditions, the issue extends to Java deployments that rely on the sandbox to isolate untrusted code, including Java Web Start applications and applets.
Root Cause
The root cause lies in improper handling of input or state within Serviceability APIs exposed by the Java runtime. These APIs can be reached indirectly, including through web services that supply data to them. Insufficient validation at this boundary allows untrusted inputs to influence runtime data integrity and resource availability.
Attack Vector
An attacker with local access invokes the vulnerable Serviceability APIs after a legitimate user performs a triggering action. In sandboxed client scenarios, loading untrusted code from the internet into a Java Web Start application or applet can lead to the same impact. The Oracle advisory classifies the issue with Integrity and Availability impacts, with no confidentiality impact.
No verified exploitation code is publicly available. Refer to the Oracle Security Alert October 2026 for technical specifics.
Detection Methods for CVE-2026-91397
Indicators of Compromise
- Unexpected invocations of Java Serviceability APIs, such as JVM Tool Interface (JVMTI) agents or diagnostic commands, on hosts not performing routine troubleshooting.
- Launches of Java Web Start (javaws) or applet containers loading JAR or JNLP content from untrusted network sources.
- Abnormal Java process termination or degraded responsiveness without a corresponding application error.
Detection Strategies
- Inventory all hosts running affected Oracle Java SE and GraalVM versions and flag any that remain unpatched after the October 2026 Oracle Critical Patch Update.
- Monitor command-line arguments for Java processes using -agentlib, -agentpath, or diagnostic flags not expected in production workloads.
- Correlate local logon events with subsequent Java process anomalies to identify the attacker-plus-user-interaction pattern required for exploitation.
Monitoring Recommendations
- Collect Java runtime telemetry, including JVM crashes, Serviceability agent loads, and JMX activity, into a centralized logging platform.
- Alert on JAR, JNLP, or applet execution originating from browsers or user download directories.
- Track process lineage for java, javaw, and javaws to identify untrusted parent processes or anomalous child spawns.
How to Mitigate CVE-2026-91397
Immediate Actions Required
- Apply the October 2026 Oracle Critical Patch Update to all affected Oracle Java SE, GraalVM for JDK, and GraalVM Enterprise Edition installations.
- Identify and remove unsupported or end-of-life Java installations that cannot receive the patch.
- Restrict local logon rights on servers running Java workloads to reduce the pool of users who meet the attack precondition.
Patch Information
Oracle addresses this vulnerability in the October 2026 Critical Patch Update. See the Oracle Security Alert October 2026 for patched version numbers for each affected product line and distribution instructions.
Workarounds
- Disable Java Web Start and applet execution on endpoints that do not require them, since sandboxed client scenarios are an in-scope attack path.
- Remove browser plugin registrations for Java and block download of JNLP files at the web proxy or email gateway.
- Enforce application allowlisting so only approved JAR files can execute, limiting exposure to untrusted code loaded from the internet.
# Verify installed Java version and remove legacy runtimes on Linux
java -version
rpm -qa | grep -Ei 'jdk|graalvm'
# Replace with the patched release from the October 2026 Oracle CPU
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

