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-87293 Overview
CVE-2026-87293 is a vulnerability in the Remote Method Invocation (RMI) component of Oracle Java SE. Oracle Java SE versions 8u503 and 8u503-perf, along with Oracle GraalVM Enterprise Edition 21.3.19.1.1, are affected. An unauthenticated attacker with network access can exploit the flaw through multiple protocols. Successful exploitation permits unauthorized update, insert, or delete access to a subset of Oracle Java SE data, as well as unauthorized read access to a subset of data. The vulnerability has a scope change, meaning attacks may significantly impact additional products beyond Java SE itself. Exploitation is considered difficult due to high attack complexity.
Critical Impact
Unauthenticated network attackers can tamper with and read a subset of Java SE accessible data through RMI, with scope-change implications for downstream products.
Affected Products
- Oracle Java SE 8u503
- Oracle Java SE 8u503-perf
- Oracle GraalVM Enterprise Edition 21.3.19.1.1
Discovery Timeline
- 2026-10-20 - CVE-2026-87293 published to NVD
- 2026-10-21 - Last updated in NVD database
- Referenced in the Oracle Security Advisory October 2026
Technical Details for CVE-2026-87293
Vulnerability Analysis
The vulnerability resides in the Remote Method Invocation (RMI) subsystem of Oracle Java SE. RMI enables Java objects to invoke methods on objects running in remote Java Virtual Machines (JVMs), making it a frequent target for deserialization and protocol-level flaws. The weakness permits an unauthenticated attacker to tamper with a subset of accessible data and read a subset of accessible data. Oracle classifies the issue as difficult to exploit, requiring specific conditions outside the attacker's control. Scope change in the CVSS vector indicates that the compromise can extend beyond the vulnerable Java SE component and affect additional products that rely on it.
Oracle notes the vulnerability is reachable only by supplying data to RMI APIs through channels such as web services. Untrusted Java Web Start applications and untrusted Java applets are not required as a delivery mechanism, which widens the viable attacker population to any party able to send data to an exposed RMI endpoint.
Root Cause
Oracle has not disclosed the specific internal cause. The description places the defect in the RMI component, consistent with historical Java SE RMI issues involving object handling, serialization boundaries, and protocol parsing. Refer to the Oracle advisory for authoritative technical specifics.
Attack Vector
An attacker leverages network reachability to an exposed RMI endpoint or a service that forwards data to RMI APIs. No authentication or user interaction is required. The attack supplies crafted data over supported protocols to the RMI component. Successful requests yield partial data disclosure and partial data modification within the targeted application and any product in scope due to the scope-change condition.
No verified public code examples are available. See the Oracle Security Advisory October 2026 for Oracle's technical guidance.
Detection Methods for CVE-2026-87293
Indicators of Compromise
- Unexpected inbound connections to RMI registry ports (default 1099) or dynamically assigned RMI object ports from untrusted networks.
- Anomalous serialized Java object payloads delivered to web services that proxy requests to RMI endpoints.
- Unexplained modifications, insertions, or deletions in application data stores accessed by Java SE processes.
Detection Strategies
- Inventory all hosts running Oracle Java SE 8u503, 8u503-perf, and Oracle GraalVM Enterprise Edition 21.3.19.1.1.
- Inspect network flows for RMI traffic traversing trust boundaries, including services that expose RMI through HTTP or other transport layers.
- Correlate Java application logs with network telemetry to identify unauthenticated requests that trigger RMI method invocations.
Monitoring Recommendations
- Alert on process behavior where Java processes spawn unexpected child processes or write to sensitive paths after receiving RMI traffic.
- Monitor outbound connections from Java processes to external hosts, which can indicate data exfiltration following exploitation.
- Centralize Java application and host telemetry in a SIEM to support cross-source correlation and historical hunting.
How to Mitigate CVE-2026-87293
Immediate Actions Required
- Apply the patches referenced in the Oracle Security Advisory October 2026 to all affected Java SE and GraalVM installations.
- Restrict network exposure of RMI endpoints to trusted management networks using firewall rules and segmentation.
- Audit services that forward external input to RMI APIs and gate them with authentication and input validation.
Patch Information
Oracle addressed CVE-2026-87293 in the October 2026 Critical Patch Update. Administrators should install the latest Oracle Java SE and Oracle GraalVM Enterprise Edition releases listed in the advisory. Downstream vendors that bundle these runtimes may ship their own updates; verify through vendor advisories.
Workarounds
- Disable RMI endpoints that are not required for application function.
- Place RMI listeners behind authenticated reverse proxies or mutual TLS to block unauthenticated access.
- Apply Java SerialFilter and jdk.serialFilter configurations to constrain acceptable classes for deserialization through RMI.
# Example: constrain Java deserialization via a global serial filter
# Add to the JVM launch command or java.security configuration
java -Djdk.serialFilter='maxbytes=16384;maxdepth=20;java.base/*;!*' \
-Dsun.rmi.registry.registryFilter='java.base/*;!*' \
-jar application.jar
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

