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-91417 Overview
CVE-2026-91417 is a network-exploitable vulnerability in the Common Object Request Broker Architecture (CORBA) component of Oracle Java SE and Oracle GraalVM Enterprise Edition. An unauthenticated attacker can trigger a partial denial of service by sending crafted data to exposed APIs over multiple protocols. The weakness is categorized as uncontrolled resource consumption [CWE-400]. Oracle disclosed the issue in the October 2026 Critical Patch Update.
Affected versions include Oracle Java SE 8u503 and 8u503-perf, and Oracle GraalVM Enterprise Edition 21.3.19.1.1. Exploitation requires no user interaction and no privileges, which lowers the barrier to automated abuse against internet-facing services that expose CORBA endpoints.
Critical Impact
Unauthenticated remote attackers can degrade availability of Java SE and GraalVM services exposing CORBA APIs through specially crafted protocol traffic.
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 CVE-2026-91417 published to NVD
- 2026-10-22 - Last updated in NVD database
Technical Details for CVE-2026-91417
Vulnerability Analysis
The flaw resides in the CORBA subsystem of Oracle Java SE and Oracle GraalVM Enterprise Edition. CORBA provides interoperable remote object invocation across heterogeneous systems using protocols such as the Internet Inter-ORB Protocol (IIOP). The vulnerability allows a remote attacker to supply crafted request data that drives the component into excessive resource consumption, producing a partial denial of service.
Oracle classifies the issue as exploitable through APIs in the CORBA component without requiring Java Web Start applications or Java applets. Delivery through a web service or any process that passes attacker-controlled data to the affected APIs is sufficient. The EPSS score at publication is 0.306% (percentile 22.169), indicating low observed exploit activity at this time.
Root Cause
The root cause is uncontrolled resource consumption [CWE-400] inside CORBA request handling. The component does not sufficiently bound memory, threads, or CPU work when parsing or dispatching certain inbound messages. Repeated or malformed requests exhaust capacity assigned to the Object Request Broker (ORB), degrading availability of the hosting Java Virtual Machine (JVM).
Attack Vector
The attack vector is network-based. An attacker reaches the vulnerable CORBA endpoint over supported protocols and submits data that triggers the resource exhaustion path. No authentication, user interaction, or local access is required. Impact is limited to availability; confidentiality and integrity are not affected according to Oracle's advisory.
No verified public proof-of-concept code is available. See the Oracle Security Alert October 2026 for the authoritative technical description.
Detection Methods for CVE-2026-91417
Indicators of Compromise
- Unexpected spikes in JVM CPU, heap, or thread utilization on hosts running CORBA services (IIOP listeners, typically TCP ports in the 1050-1055 range or custom ORB ports).
- Repeated inbound IIOP connections or malformed GIOP messages from a narrow set of source addresses.
- OutOfMemoryError or thread-pool exhaustion entries in Java application logs correlated with external traffic bursts.
Detection Strategies
- Inventory all Java SE 8u503, 8u503-perf, and GraalVM EE 21.3.19.1.1 deployments and flag any instance exposing CORBA/IIOP endpoints to untrusted networks.
- Deploy network signatures that identify anomalous GIOP/IIOP request volume or oversized message framing against inventoried ORB ports.
- Correlate application-tier availability degradation with concurrent network traffic to CORBA listeners to distinguish attacks from capacity issues.
Monitoring Recommendations
- Alert on JVM thread count, heap pressure, and garbage collection pause times exceeding baseline on CORBA-enabled services.
- Capture NetFlow or packet metadata for ORB ports and retain for retrospective hunting if availability events occur.
- Monitor Oracle's security alerts page for updates and additional affected version disclosures.
How to Mitigate CVE-2026-91417
Immediate Actions Required
- Apply the fixes from the October 2026 Oracle Critical Patch Update to Java SE and GraalVM Enterprise Edition installations.
- Restrict network reachability of CORBA/IIOP endpoints to trusted management segments using host and network firewalls.
- Where CORBA is not required, disable the ORB and remove exposed listeners from affected JVM processes.
Patch Information
Oracle addressed CVE-2026-91417 in the October 2026 Critical Patch Update. Administrators should upgrade Oracle Java SE beyond 8u503 and 8u503-perf, and Oracle GraalVM Enterprise Edition beyond 21.3.19.1.1, following the versions listed in the Oracle Security Alert October 2026.
Workarounds
- Place rate limiting and connection quotas in front of CORBA listeners to blunt resource exhaustion attempts.
- Terminate IIOP connections from untrusted sources at a reverse proxy or network ACL until patching completes.
- Enforce JVM resource ceilings (-Xmx, thread pool bounds, request timeouts) to contain the blast radius of a successful DoS attempt.
# Example iptables rule limiting inbound IIOP connections to a trusted subnet
iptables -A INPUT -p tcp --dport 1050 -s 10.10.0.0/24 -j ACCEPT
iptables -A INPUT -p tcp --dport 1050 -j DROP
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

