Automated Threat Modeling

Brief Summary: CVE-2026-91566, an Authenticated HTTP Takeover Flaw in Oracle Service Bus Core

A brief summary of CVE-2026-91566, a CVSS 8.8 flaw in the Core component of Oracle Service Bus 12.2.1.4.0 and 14.1.2.0.0 that lets a low-privileged HTTP attacker take over the product. Includes patch delivery and verification notes from the November 2026 Oracle Critical Security Patch Update.

CVE Analysis

7 min read

Gaurav Sarraf
Gaurav Sarraf

2026-11-17

Brief Summary: CVE-2026-91566, an Authenticated HTTP Takeover Flaw in Oracle Service Bus Core

Introduction

Oracle Service Bus sits between the services and applications that many enterprise workflows depend on, so a flaw that lets an authenticated user take over the bus itself deserves prompt attention from middleware teams. Oracle's November 2026 Critical Security Patch Update addresses CVE-2026-91566, a High-severity (CVSS 3.1 8.8) issue in the Service Bus Core component that a low-privileged attacker can reach over HTTP.

Oracle Service Bus (OSB) is an integration product within Oracle Fusion Middleware. Oracle describes it as connecting, virtualizing, and managing interactions between services and applications in mission-critical, service-oriented architecture environments. Its documentation lists message validation, transformation, and routing, together with security services such as authentication, authorization, auditing, and credential mapping. The sources we reviewed do not give an OSB installed-base or market-share figure. Oracle's page on Gartner's May 19, 2025 Magic Quadrant places Oracle as a Challenger in Integration Platform as a Service, but that is a dated iPaaS market assessment, not a measure of OSB deployments or security posture.

Technical information

What Oracle disclosed

Oracle's description is short. It states that the issue is an "easily exploitable vulnerability" that "allows low privileged attacker with network access via HTTP to compromise Oracle Service Bus," and that "successful attacks of this vulnerability can result in takeover of Oracle Service Bus." The Fusion Middleware risk matrix in the November 2026 advisory lists the protocol as HTTP, marks the issue as not remotely exploitable without authentication, and carries no product-specific notes for this CVE.

Root cause: not publicly disclosed

This is a closed-source vendor fix, and Oracle has not said which code path in the Core component changed. No CWE has been assigned, and the NVD record is still in Received status with no NVD-assigned score or CWE. The 8.8 score is Oracle's own CNA assessment. No primary record we reviewed identifies an affected URL, HTTP method, request parameters, vulnerable function, required account role, or exploit payload.

VulDB labels the issue "privileges management" and maps it to MITRE ATT&CK T1068, but the same entry states that technical details are unknown. We treat that as a third-party classification, not a confirmed root cause. Without vendor-published diffs, any more specific root cause description is speculation, so we do not offer one here.

CVSS vector breakdown

The published vector is:

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
  • Attack Vector: Network. The attack is network reachable, and Oracle names HTTP as the access protocol.
  • Attack Complexity: Low. FIRST defines this as requiring no specialized access conditions or extenuating circumstances.
  • Privileges Required: Low. Basic privileges are needed. The specific OSB role or permission is not disclosed.
  • User Interaction: None. No action by another user is needed.
  • Scope: Unchanged. The impact is scored against OSB itself.
  • Confidentiality, Integrity, Availability: High. Consistent with Oracle's "takeover" wording.

For triage, low complexity does not mean no authentication. An existing low-privileged position on OSB is part of the published attack conditions, which distinguishes this issue from unauthenticated Oracle middleware bugs with different prerequisites.

Attack flow as documented

Based only on what Oracle published, the exploitation model looks like this:

  1. The attacker has HTTP network reachability to an OSB instance running 12.2.1.4.0 or 14.1.2.0.0.
  2. The attacker holds low-privileged credentials on that instance. Which role is sufficient has not been disclosed.
  3. The attacker sends HTTP traffic that triggers the flaw in the Core component. The triggering request has not been disclosed.
  4. A successful attack can result in takeover of Oracle Service Bus, with high impact on confidentiality, integrity, and availability. No victim interaction is required.

OSB often acts as the integration hub between backend systems, which is why a takeover of the bus matters. The CVE itself, however, only establishes potential takeover of OSB. It does not establish compromise of any particular connected database or application.

Exploitation status

Active exploitation is not confirmed in the reviewed sources. Rapid7 marks its CISA KEV field as false, and TheHackerWire states the CVE is not recorded in KEV. TheHackerWire reports no confirmed public exploit code, and VulDB says an exploit is not publicly available. Rapid7 lists EPSS score and percentile as unavailable and discloses no exploit module. No threat actor has been linked to this CVE. These findings describe the state of public reporting, not complete visibility into adversary activity.

Patch information

Oracle fixed CVE-2026-91566 in its November 2026 Critical Security Patch Update (CSPU), released on 17 November 2026. There is no public commit, diff or changelog, so this section covers how the fix is delivered and how to confirm it is installed.

What Oracle published

  • Advisory: The CVE is listed in the Fusion Middleware risk matrix of the November 2026 CSPU, which Oracle says contains 71 new security patches for Fusion Middleware.
  • Patched release lines: OSB 12.2.1.4.0 and 14.1.2.0.0, the only two supported versions Oracle lists as affected. One upstream summary also named 12.2.1.5.0 and mentioned PHP. Neither Oracle's advisory, its CSAF data nor the NVD record supports that, so it should be disregarded.
  • Risk matrix entry: protocol HTTP, not remotely exploitable without authentication, CVSS 3.1 score 8.8 with the vector shown above.
  • Where to get the patch: Oracle's CSAF file (cspunov2026csaf.json) lists the fix as a vendor_fix for both release lines and points to My Oracle Support document CPU450, the Fusion Middleware Patch Availability Document. It states the fix is only for "Oracle customers with valid support contracts."

How the fix is delivered

Oracle does not ship CSPU fixes as a new OSB version number. The fix arrives as patches applied with OPatch on top of an existing 12.2.1.4.0 or 14.1.2.0.0 Oracle Home. The exact patch numbers are in CPU450, which requires a support login, so we cannot list them here. In practice:

  1. Log in to My Oracle Support and open CPU450.
  2. Find the Oracle Service Bus entry for your release line (12.2.1.4.0 or 14.1.2.0.0).
  3. Apply the listed patch or patches to every Oracle Home running OSB, following Oracle's usual Fusion Middleware patching steps. That normally means stopping the managed servers and Admin Server, running OPatch, and restarting. CPU450 may also list prerequisite patches for the underlying WebLogic/FMW stack. Apply those as well.
  4. Confirm installation on each host:
opatch lspatches opatch lsinventory

Check that the patch IDs from CPU450 appear in the output. The OSB version string will not change after patching, so the OPatch inventory is the only reliable proof the fix is in place.

Interim measures and their limits

Oracle's advisory states that blocking network protocols required by an attack, or removing unnecessary privileges or access to required packages, may reduce the risk of a successful attack until patches are applied. Oracle also notes that these changes may break application functionality, should be tested on nonproduction systems first, and do not correct the underlying problem. Oracle has not published the specific privilege or endpoint involved, so there is no CVE-specific blocking rule to recommend. Treat these only as temporary exposure reduction while patching is scheduled.

Affected systems and versions

  • Product: Oracle Service Bus, part of Oracle Fusion Middleware
  • Component: Core
  • Affected supported versions: 12.2.1.4.0 and 14.1.2.0.0
  • Exploitable configuration: an OSB instance reachable over HTTP by an attacker who holds low-privileged access

Three points affect scoping:

  • Both listed releases are affected, so moving from one listed release to the other is not a fix. The applicable CPU450 patch is the remediation path.
  • The record does not establish that other OSB releases are unaffected. Oracle notes that unsupported releases are not tested for the vulnerabilities addressed in the advisory, so staying on a supported version is what keeps patches available.
  • The 12.2.1.5.0 claim seen in one upstream summary is not supported by Oracle or NVD data.

Vendor security history

Oracle runs a formal security fixing program. Its policy describes quarterly Critical Patch Updates, possible patches outside that schedule for particularly critical vulnerabilities or reported active exploitation, and cumulative fixes "as much as possible," with some products receiving individual patches instead. The November 2026 advisory separately describes security patch releases on the third Tuesday of each month, and security updates are available to active Oracle Support customers through My Oracle Support.

Oracle middleware has been targeted before. The Cyber Security Agency of Singapore reported active exploitation of CVE-2020-14750 in Oracle WebLogic Server and advised affected users to install updates immediately. That case involved an unauthenticated HTTP attacker, while CVE-2026-91566 requires low privileges. It provides context, not attribution or exploitation evidence for this Service Bus issue.

Oracle itself reports that attackers have sometimes succeeded because customers failed to apply already-available patches. The patch mechanism exists, so the remaining risk sits in deployment. That is why confirming CPU450 patches via the OPatch inventory is worth the effort.

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