CVE-2026-91615 Overview
CVE-2026-91615 is a vulnerability in the Java VM component of Oracle Database Server. The flaw affects supported versions 19.3-19.32, 21.3-21.23, and 23.4.0-23.26.3. A low-privileged attacker with network access via SOCKS5 can exploit the issue to compromise the Java VM. The attack requires high complexity but produces a scope change, meaning successful exploitation can affect components beyond the vulnerable Java VM. Successful attacks can result in unauthorized creation, deletion, or modification of critical data or all Java VM accessible data.
Critical Impact
Attackers who clear the high-complexity bar can tamper with data integrity across Java VM accessible objects, with impact extending beyond the Oracle Database Server scope.
Affected Products
- Oracle Database Server Java VM versions 19.3 through 19.32
- Oracle Database Server Java VM versions 21.3 through 21.23
- Oracle Database Server Java VM versions 23.4.0 through 23.26.3
Discovery Timeline
- 2026-10-20 - CVE-2026-91615 published to the National Vulnerability Database (NVD)
- 2026-10-21 - Last updated in NVD database
- October 2026 - Addressed in the Oracle Security Alert - October 2026
Technical Details for CVE-2026-91615
Vulnerability Analysis
The vulnerability resides in the Java VM component embedded in Oracle Database Server. An attacker leveraging a SOCKS5 network path with low privileges can interact with the Java VM in a way that permits unauthorized write operations against Java VM accessible data. The vulnerability has integrity-only impact, with no confidentiality or availability consequences reported. The scope change indicates that resources managed by components beyond the Java VM may be affected when exploitation succeeds. Exploitation is rated difficult, reflecting conditions outside the attacker's direct control such as timing, configuration, or required network reachability through SOCKS5.
Root Cause
Oracle has not published a detailed root-cause breakdown in the public advisory. The vendor summary attributes the issue to the Java VM component and indicates the flaw permits integrity violations initiated over the network. Specific affected classes, interfaces, or internal routines are not disclosed in the Oracle Security Alert.
Attack Vector
The attack originates from the network and requires that the attacker reach the Java VM through SOCKS5. The attacker must hold a low-privileged account on the target database environment. User interaction is not required. Once the preconditions are met, the attacker performs operations that result in creation, deletion, or modification of data accessible to the Java VM.
No verified proof-of-concept code is published for CVE-2026-91615. Readers requiring technical specifics should consult the Oracle Security Alert - October 2026.
Detection Methods for CVE-2026-91615
Indicators of Compromise
- Unexpected SOCKS5 traffic reaching Oracle Database Server hosts, particularly from untrusted network segments.
- Unexplained creation, deletion, or modification of objects managed by the Oracle Java VM.
- Database audit records showing low-privileged accounts invoking Java VM functionality outside normal application patterns.
Detection Strategies
- Enable Oracle Database Unified Auditing for Java VM actions and privilege use by low-privileged accounts.
- Correlate database audit events with network telemetry to flag Java VM activity initiated through proxy or SOCKS5 paths.
- Baseline normal Java stored procedure invocations and alert on deviations originating from non-application accounts.
Monitoring Recommendations
- Monitor egress and ingress for SOCKS5 (TCP/1080 or alternate ports) on database tiers that should not permit proxied traffic.
- Track grants and use of JAVAUSERPRIV, JAVASYSPRIV, and JAVADEBUGPRIV roles.
- Forward database and host telemetry to a centralized data lake and apply detection rules for integrity-impact patterns on Java VM objects.
How to Mitigate CVE-2026-91615
Immediate Actions Required
- Apply the fixes shipped in the Oracle Security Alert - October 2026 to all affected database instances.
- Inventory Oracle Database Server deployments and confirm versions against the affected ranges 19.3-19.32, 21.3-21.23, and 23.4.0-23.26.3.
- Review and reduce low-privileged accounts that retain Java VM execution rights.
Patch Information
Oracle addressed CVE-2026-91615 in the October 2026 Critical Patch Update. Review the Oracle advisory for the specific patch bundle that applies to each affected release train (19.x, 21.x, 23.x) and schedule deployment through standard database patching procedures.
Workarounds
- Block SOCKS5 egress and ingress on database network segments where it is not required.
- Restrict database network reachability using firewall rules, Oracle Net ACLs, and tcp.invited_nodes entries in sqlnet.ora.
- Revoke Java execution privileges from accounts that do not require them, using least-privilege principles for Java VM access.
# Example sqlnet.ora network restriction (illustrative)
tcp.validnode_checking = yes
tcp.invited_nodes = (10.0.0.0/24, 10.0.1.0/24)
tcp.excluded_nodes = (0.0.0.0/0)
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

