Automated Threat Modeling

Overview of CVE-2026-91561: Low-Privilege RMI Flaw in Oracle Service Bus Core Exposes Critical Data

A brief summary of CVE-2026-91561, a CVSS 9.6 flaw in the Oracle Service Bus Core component that lets a low-privileged attacker with RMI network access read and modify critical data. It covers affected releases, what can be inferred about the root cause, and the patch details from Oracle's November 2026 Critical Security Patch Update.

CVE Analysis

7 min read

Gaurav Sarraf
Gaurav Sarraf

2026-11-17

Overview of CVE-2026-91561: Low-Privilege RMI Flaw in Oracle Service Bus Core Exposes Critical Data

Introduction

Oracle's November 2026 Critical Security Patch Update fixes a flaw in Oracle Service Bus that lets an authenticated user holding only low privileges read, create, modify or delete critical data reachable by Service Bus, using nothing more than network access over RMI. Oracle rates the issue as scope changed, so the impact is not necessarily confined to Service Bus itself. That matters for an integration layer that sits between many other enterprise systems.

Oracle Service Bus is part of Oracle Fusion Middleware. Oracle documents it as a core component of Oracle SOA Suite that acts as a backbone for SOA messaging, connecting, mediating and managing interactions among heterogeneous services, legacy applications, packaged applications and other enterprise service bus instances. Oracle positions it for mission-critical SOA environments where performance, scalability and reliability matter, although the sources we reviewed do not give a numerical market share for the product. For broader context, Oracle states that Gartner named it a Challenger in the 2025 Magic Quadrant for Integration Platform as a Service, which is an iPaaS assessment rather than a Service Bus ranking or a security evaluation.

Technical information

What Oracle disclosed

CVE-2026-91561 affects the Core component of Oracle Service Bus. Oracle's CNA record describes an easily exploitable vulnerability that allows a low-privileged attacker with network access via RMI to compromise Oracle Service Bus. The published CVSS 3.1 vector is:

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:N

Reading that vector against the FIRST CVSS v3.1 specification:

  • Attack vector: Network
  • Attack complexity: Low
  • Privileges required: Low
  • User interaction: None
  • Scope: Changed
  • Confidentiality impact: High
  • Integrity impact: High
  • Availability impact: None

The resulting base score of 9.6 falls in FIRST's 9.0 to 10.0 Critical band. CVSS base scores measure intrinsic severity, not the probability that a given deployment will be attacked.

Oracle lists two outcomes: unauthorized creation, deletion or modification of critical data or all data accessible to Oracle Service Bus, and unauthorized access to critical data or complete access to all data accessible to Oracle Service Bus. Oracle also warns that attacks may significantly impact additional products, but it does not name those products in the CVE description.

Root cause: what can and cannot be inferred

Oracle Service Bus is closed source, so there is no public commit or diff to study, and Oracle does not publish root cause details. The CNA record and the CSAF file list no CWE. VulDB separately assigns CWE-285 (Improper Authorization), but that is a third-party classification, not one supplied by Oracle.

The disclosed conditions still narrow things down. The vulnerable code is reachable over RMI by a caller who is already authenticated with low privileges, a successful attack yields full read and write access to data that Service Bus can reach, and the scope-changed rating means the impact crosses beyond Service Bus. Taken together, that points to an access control or trust boundary weakness on an RMI-exposed Service Bus interface. The fix is most likely a server-side check that stops low-privileged RMI callers from performing operations or reaching data they are not authorized for. This is an inference. Oracle has not confirmed the mechanism.

The record also does not support some of the ways a flaw like this gets described. With availability impact rated None and only confidentiality and integrity impacts documented, nothing in the public material justifies calling this remote code execution, server takeover or denial of service.

Attack flow

Based solely on the conditions Oracle published, exploitation looks like this:

  1. The attacker holds a low-privileged account that can authenticate to the Service Bus environment. Unauthenticated exploitation is not described.
  2. The attacker has network reach to the RMI interface exposed by the affected Service Bus deployment.
  3. The attacker issues RMI calls to the vulnerable Core functionality. Attack complexity is low and no action by another user is required.
  4. The server processes the request without enforcing the expected restrictions, giving the attacker read access to critical data or all data accessible to Service Bus, and the ability to create, delete or modify that data.
  5. Because scope is changed, the effects can extend into additional products that depend on or are reached through Service Bus.

The specific RMI method, request sequence, payload and the exact privilege that is sufficient are not publicly disclosed.

Exploitation status

The reviewed reporting does not establish exploitation in the wild. TheHackerWire states that no public proof of concept was detected and no public exploit code had been confirmed, and it shows no EPSS score yet. No threat actor, campaign or malware family has been attributed to this CVE.

The CISA Known Exploited Vulnerabilities snapshot we reviewed (catalog version 2026.11.17) was released at 17:53 UTC on 17 November 2026, while Oracle's CNA record was published at 21:34 UTC the same day. The absence of a KEV entry in that snapshot therefore tells us very little. Unconfirmed exploitation is not the same as confirmed inactivity, and none of this changes Oracle's recommendation to patch promptly.

Patch information

Oracle fixed CVE-2026-91561 in its November 2026 Critical Security Patch Update (CSPU), first published on 17 November 2026 as Rev 1. The fix ships as a binary patch through My Oracle Support. The details below come from Oracle's advisory, the text form of its risk matrix and its machine-readable CSAF file.

What the patch covers

  • Product and component: Oracle Service Bus (Oracle Fusion Middleware), component Core
  • Fixed versions: supported releases 12.2.1.4.0 and 14.1.2.0.0
  • Attack protocol: RMI (Java Remote Method Invocation)
  • Remotely exploitable without authentication: No, a low-privileged account is required
  • CVSS 3.1: 9.6, CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:N
  • CSAF remediation type: vendor_fix for Oracle customers with valid support contracts
  • Patch Availability Document: My Oracle Support Note CPU450 (Fusion Middleware), with an executive summary in Note CPU433

This CVE is one of 71 new Fusion Middleware security fixes in the November 2026 CSPU. Oracle does not release a separate hotfix per CVE. The fix is folded into the bundle and stack patches for each Fusion Middleware release, and Note CPU450 maps each affected release to the exact patch numbers and provides the installation instructions. Oracle describes CSPUs as targeted updates that complement its quarterly cumulative Critical Patch Updates.

Eligibility and prerequisites

  • Oracle builds CSPU patches only for versions in Premier or Extended Support under its Lifetime Support Policy. Releases outside those phases, such as older 12.2.1.x builds, receive no fix and need an upgrade to 12.2.1.4.0 or 14.1.2.0.0 first.
  • Patches are downloaded with a support contract through the Patch Availability Document. Oracle tells customers to stay on actively supported versions and apply the patches without delay.
  • The October 2026 CPU also contained Oracle Service Bus Core fixes, for example CVE-2026-87369, an HTTP-based issue. The November CSPU sits on top of those, so environments that skipped the October patches should check CPU450 for any prerequisite patches.

Verifying the fix

Run the following against the Fusion Middleware Oracle Home that hosts Service Bus, then compare the output with the November 2026 patch numbers listed in Note CPU450 for your release:

opatch lspatches opatch lsinventory

Fixes delivered in the Service Bus or SOA bundle patches only take effect after the managed servers are restarted. The protection exists only once the binary patch is applied to the Service Bus Oracle Home.

Interim risk reduction

Oracle's advisory notes that, until patches are applied, blocking the network protocols an attack requires and removing privileges or package access from users who do not need them may reduce risk. Oracle also warns that both measures may break application functionality, strongly recommends testing them outside production, and states that neither corrects the underlying problem. The CVE identifies RMI as the attack protocol, but Oracle does not publish a specific port, firewall rule or exact role to revoke, so these controls need to be designed around your own deployment and treated strictly as temporary.

Affected systems and versions

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

Vulnerable configurations are those where the Service Bus RMI interface is reachable over the network by an attacker who holds a low-privileged account. Oracle lists only supported releases. Versions outside Premier or Extended Support are not evaluated and will not receive a fix, so they should be treated as requiring an upgrade to a supported release before patching.

Vendor security history

Oracle's middleware has a documented history of exploited vulnerabilities. CVE-2019-2725 was a WebLogic Server deserialization flaw that Oracle's security alert describes as enabling remote code execution without authentication. Oracle issued an out-of-band Security Alert and urged customers to apply it as soon as possible. Trend Micro later reported confirmed exploitation of CVE-2019-2725 to deliver a Monero cryptocurrency miner, describing activity observed on 10 June 2019. That case differs materially from CVE-2026-91561, which requires low privileges and documents data confidentiality and integrity impacts, and it is not evidence of shared root causes, payloads or threat actors.

Oracle Service Bus Core itself received fixes in the October 2026 CPU, including CVE-2026-87369, an HTTP-based issue, only a month before this RMI-based flaw.

On process, Oracle describes its quarterly Critical Patch Update program as the primary mechanism for delivering security fixes to supported releases, with Security Alerts reserved for highly critical and urgent threats and Critical Security Patch Updates providing targeted fixes between quarterly releases. Oracle makes CPUs cumulative where possible but delivers individual patches for some products, and it does not provide fixes for versions outside support.

References

Detect & fix
what others miss

Works with
  • GitHub
  • GitLab
  • Bitbucket
  • Azure DevOps Services
  • Gerrit
  • CVS
  • Jira
  • Linear
  • Slack
  • Security Compass
Explore integrations
Security magnifying glass visualization