Skip to main content
Vulnerability Database/CVE-2026-87364

CVE-2026-87364: Oracle Service Bus RCE Vulnerability

CVE-2026-87364 is a remote code execution vulnerability in Oracle Service Bus that allows low-privileged attackers to take over the system. This article covers technical details, affected versions, and mitigation.

Published:

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-87364 Overview

CVE-2026-87364 is a high-severity vulnerability in the Core component of Oracle Service Bus, part of Oracle Fusion Middleware. The flaw affects supported versions 12.2.1.4.0 and 14.1.2.0.0. A low-privileged attacker with network access over HTTP can exploit the issue without user interaction. Successful exploitation results in full takeover of Oracle Service Bus, impacting confidentiality, integrity, and availability. Oracle addressed the vulnerability in the October 2026 Critical Patch Update.

Critical Impact

Authenticated attackers with low privileges can remotely compromise Oracle Service Bus over HTTP and obtain complete control of the service.

Affected Products

  • Oracle Service Bus 12.2.1.4.0
  • Oracle Service Bus 14.1.2.0.0
  • Oracle Fusion Middleware (Core component)

Discovery Timeline

  • 2026-10-20 - CVE-2026-87364 published to the National Vulnerability Database (NVD)
  • 2026-10-21 - Last updated in NVD database
  • October 2026 - Oracle addresses the issue in the Oracle Critical Patch Update October 2026

Technical Details for CVE-2026-87364

Vulnerability Analysis

The vulnerability resides in the Core component of Oracle Service Bus, a middleware product that mediates message exchange between heterogeneous enterprise services. An attacker with a low-privileged account can send crafted HTTP requests to the Service Bus endpoint. The request path allows the attacker to bypass intended component boundaries and perform operations beyond their authorization level. Successful exploitation yields high impact to confidentiality, integrity, and availability, culminating in full product takeover. Because Oracle Service Bus commonly brokers traffic between back-end systems, a compromised instance can be used to pivot into integrated applications and data stores.

Root Cause

Oracle has not published root-cause details beyond the advisory text. The description indicates the flaw is in the Core component and is reachable over HTTP by a low-privileged user. Based on CVSS metrics, the issue requires authentication but no user interaction, and no scope change occurs. The patch is distributed through the Oracle Critical Patch Update October 2026.

Attack Vector

The attack vector is network-based over HTTP. Any user with valid low-privileged credentials to the Oracle Service Bus management or runtime interface can trigger exploitation. The low attack complexity means the exploit is reliable and does not require specialized conditions. Oracle Service Bus deployments exposed to internal corporate networks are reachable by any authenticated user, which broadens the realistic attacker population to insiders and attackers who have obtained a foothold.

No public exploit code or proof-of-concept has been published at this time. See the Oracle Critical Patch Update October 2026 for vendor-provided details.

Stop Remote Code Execution Before It Runs

Singularity™ Endpoint detects and blocks exploit attempts at machine speed, including zero-days and novel attack techniques.

Stop Exploit Attempts

Detection Methods for CVE-2026-87364

Indicators of Compromise

  • Unexpected HTTP requests to Oracle Service Bus administrative or runtime endpoints from low-privileged user accounts.
  • New or modified Service Bus proxy services, business services, or pipelines that were not deployed through change control.
  • Outbound connections from the Service Bus host to unfamiliar destinations following suspicious HTTP activity.
  • WebLogic Server audit logs showing privilege operations performed by accounts that should not possess them.

Detection Strategies

  • Review Oracle Service Bus and underlying WebLogic access logs for anomalous POST or PUT requests from non-administrative accounts.
  • Correlate authentication events with configuration-change events to identify low-privileged accounts triggering administrative actions.
  • Baseline normal Service Bus deployment and management activity, then alert on deviations.

Monitoring Recommendations

  • Forward WebLogic, Service Bus, and host operating system logs to a centralized analytics platform for retention and correlation.
  • Monitor process creation and child-process activity on Service Bus hosts for unexpected shells or scripting interpreters.
  • Alert on new administrative role assignments or credential changes within the Oracle Service Bus domain.

How to Mitigate CVE-2026-87364

Immediate Actions Required

  • Apply the Oracle Critical Patch Update October 2026 to all Oracle Service Bus 12.2.1.4.0 and 14.1.2.0.0 instances.
  • Inventory all Oracle Fusion Middleware deployments and confirm patch status against Oracle's advisory.
  • Restrict network access to Oracle Service Bus HTTP endpoints so only required administrative networks can reach them.
  • Audit user accounts with access to Service Bus and remove unneeded low-privileged accounts.

Patch Information

Oracle released fixes for CVE-2026-87364 as part of the Oracle Critical Patch Update October 2026. Review the advisory for specific patch identifiers that correspond to Oracle Service Bus 12.2.1.4.0 and 14.1.2.0.0. Apply the patches during the next approved maintenance window and validate functionality in a staging environment first.

Workarounds

  • Place Oracle Service Bus behind a reverse proxy or web application firewall that enforces strict authentication and request filtering.
  • Enforce network segmentation so Service Bus management interfaces are not reachable from general user networks.
  • Rotate credentials for all Service Bus accounts and enforce strong password or federated authentication policies.
  • Enable detailed WebLogic audit logging on Service Bus hosts until patches are applied.
bash
# Configuration example: restrict Oracle Service Bus HTTP endpoint access with iptables
iptables -A INPUT -p tcp --dport 7001 -s 10.0.10.0/24 -j ACCEPT
iptables -A INPUT -p tcp --dport 7001 -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

Experience the Most Advanced Cybersecurity Platform

See how the world’s most intelligent, autonomous cybersecurity platform can protect your organization today and into the future.