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

CVE-2026-87359: Oracle Service Bus RCE Vulnerability

CVE-2026-87359 is a remote code execution vulnerability in Oracle Service Bus that enables low-privileged attackers to fully compromise the system. This article covers the 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-87359 Overview

CVE-2026-87359 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 the Oracle Service Bus instance, with impact to confidentiality, integrity, and availability. Oracle addressed the issue in the October 2026 Critical Patch Update.

Critical Impact

Authenticated remote attackers can fully compromise Oracle Service Bus deployments, exposing enterprise integration flows, credentials, and backend services to tampering and disclosure.

Affected Products

  • Oracle Service Bus 12.2.1.4.0
  • Oracle Service Bus 14.1.2.0.0
  • Oracle Fusion Middleware deployments embedding the affected Service Bus Core component

Discovery Timeline

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

Technical Details for CVE-2026-87359

Vulnerability Analysis

The vulnerability resides in the Core component of Oracle Service Bus, the integration layer responsible for message routing, transformation, and service virtualization across Oracle Fusion Middleware. Exploitation requires an authenticated session with low privileges and network reachability to the Service Bus HTTP interface. The attack scope is unchanged, meaning compromise is contained within the Service Bus security boundary, yet that boundary includes brokered credentials and downstream service endpoints.

A successful attack grants control over the Service Bus runtime, enabling an adversary to modify message pipelines, intercept in-flight payloads, and pivot to backend applications integrated through the bus. The CVSS metrics indicate high impact to confidentiality, integrity, and availability.

Root Cause

Oracle has not published the detailed root cause. Based on the vector CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H, the defect is reachable through standard HTTP interactions and does not depend on complex preconditions. Oracle Service Bus flaws of this class historically map to authorization gaps, insecure deserialization, or management-interface abuse in the Core processing stack. Refer to the Oracle Critical Patch Update October 2026 for authoritative details.

Attack Vector

The attacker initiates HTTP requests to the Service Bus with any valid low-privileged credential. No user interaction is required. Because Service Bus often sits in trusted zones between application tiers, exploitation can lead to lateral movement into databases, enterprise service bus consumers, and SOAP or REST backends mediated by the platform.

No public proof-of-concept exploit code is available at the time of publication. The EPSS probability is 0.447% with a percentile of 37.821 as of 2026-10-22.

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-87359

Indicators of Compromise

  • Unexpected HTTP POST or PUT requests to Service Bus management or proxy service endpoints originating from low-privileged accounts.
  • Creation or modification of proxy services, business services, or pipeline resources outside change-management windows.
  • New or altered outbound connections from the Service Bus runtime to unknown hosts.
  • Anomalous use of WebLogic administrative APIs or sbconsole paths from non-admin principals.

Detection Strategies

  • Correlate Service Bus audit logs with WebLogic access logs to identify low-privilege sessions issuing configuration-changing calls.
  • Baseline normal pipeline deployment activity and alert on deviations in frequency, source IP, or user identity.
  • Monitor for unexpected Java process behavior on the Service Bus host, including child process creation or outbound socket activity from the managed server JVM.

Monitoring Recommendations

  • Forward WebLogic Server, Service Bus, and operating system logs to a centralized analytics platform for correlation.
  • Alert on authentication events for low-privileged Service Bus accounts followed by administrative-scope operations.
  • Track egress traffic from Fusion Middleware subnets and flag connections to non-approved destinations.

How to Mitigate CVE-2026-87359

Immediate Actions Required

  • Apply the October 2026 Oracle Critical Patch Update to all Oracle Service Bus 12.2.1.4.0 and 14.1.2.0.0 deployments.
  • Inventory all Fusion Middleware hosts running Service Bus and confirm patch coverage after deployment.
  • Rotate credentials for Service Bus accounts, especially low-privileged service users exposed to networked clients.
  • Review Service Bus configuration for unauthorized proxy services, pipelines, or alert destinations created before patching.

Patch Information

Oracle released the fix as part of the Oracle Critical Patch Update October 2026. Administrators should follow Oracle's documented patching procedure for Fusion Middleware, including backups of the domain configuration and validation of managed server restart ordering.

Workarounds

  • Restrict network access to Service Bus HTTP endpoints using firewall rules, reverse proxies, or network segmentation until patching completes.
  • Enforce least-privilege role assignment for all Service Bus and WebLogic users; remove unused accounts.
  • Require mutual TLS or an authenticating gateway in front of Service Bus proxy services exposed beyond trusted integration zones.
  • Enable Service Bus and WebLogic auditing at verbose levels to improve forensic visibility while remediation is validated.
bash
# Example: restrict access to Service Bus management ports with iptables
# Replace 10.0.0.0/24 with your trusted administration subnet
iptables -A INPUT -p tcp --dport 7001 -s 10.0.0.0/24 -j ACCEPT
iptables -A INPUT -p tcp --dport 7001 -j DROP
iptables -A INPUT -p tcp --dport 8011 -s 10.0.0.0/24 -j ACCEPT
iptables -A INPUT -p tcp --dport 8011 -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.