Automated Threat Modeling

Brief Summary: Oracle BI Enterprise Edition CVE-2026-114784, an Unauthenticated Platform Security Takeover Rated CVSS 10.0

A brief summary of CVE-2026-114784, a CVSS 10.0 flaw in the Platform Security component of Oracle Business Intelligence Enterprise Edition that allows unauthenticated takeover over HTTP. The post covers what Oracle has disclosed, the affected versions, and how to obtain the November 2026 CSPU patch.

CVE Analysis

7 min read

Gaurav Sarraf
Gaurav Sarraf

2026-11-17

Brief Summary: Oracle BI Enterprise Edition CVE-2026-114784, an Unauthenticated Platform Security Takeover Rated CVSS 10.0

Introduction

Oracle's November 2026 Critical Security Patch Update (CSPU) fixes a flaw in Oracle Business Intelligence Enterprise Edition (OBIEE) that allows an unauthenticated attacker with HTTP access to take over the product. Rated CVSS 3.1 10.0 with a changed scope, CVE-2026-114784 sits at the top of the severity scale, and Oracle warns that successful attacks may significantly impact additional products beyond OBIEE itself.

OBIEE is part of Oracle Analytics, a platform that Oracle documents as connecting to data across public cloud, private cloud, local environments, databases and personal datasets, with role-based authorization and data-level access controls. A takeover of its Platform Security component is therefore relevant to whatever an organization has wired into its analytics layer. That is business context only. The public record does not prove that any specific connected data source can be compromised through this flaw.

This post summarizes what Oracle, NVD and third-party trackers have disclosed, and is explicit about what has not been disclosed.

Technical information

Component and root cause

The vulnerability is in the Platform Security component of OBIEE. Oracle's description is short. It says an easily exploitable vulnerability allows an unauthenticated attacker with network access via HTTP to compromise OBIEE, and that successful attacks can result in takeover of the product.

The underlying defect is not public. Specifically:

  • Oracle and NVD do not disclose the vulnerable endpoint, request structure, payload, implementation defect or exploit chain.
  • NVD lists no CWE for this CVE, so the weakness class (injection, deserialization, authentication bypass or something else) is not established.
  • VulDB files the entry under "privileges management" in its title, but also reports that neither technical details nor an exploit are publicly available.

Because OBIEE is closed source and Oracle does not publish diffs, there is no vulnerable code to show. We also want to be careful with wording. "Takeover" is Oracle's term, and it should not be rewritten as a confirmed arbitrary operating system command execution primitive.

What the CVSS vector establishes

Oracle, acting as the CNA, published the vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H. Read against the FIRST CVSS 3.1 specification:

  • AV:N (Network): exploitable over the network. Oracle names HTTP as the protocol.
  • AC:L (Low complexity): Oracle also describes it as easily exploitable.
  • PR:N (No privileges): the attacker needs no prior account or privileges on OBIEE.
  • UI:N (No user interaction): no other user has to click or do anything.
  • S:C (Changed scope): impact can cross the security scope of the vulnerable component and reach other components or products.
  • C:H / I:H / A:H: high impact to confidentiality, integrity and availability.

The 10.0 is Oracle's score. NVD states that its own assessment has not yet been provided. A maximum base score describes severity, not evidence of attacks.

Attack flow

Based only on what Oracle has published, the attack path looks like this:

  1. The attacker has HTTP network reach to an OBIEE instance running version 8.2.0.0.0 or 26.01.0.0.0.
  2. Without credentials and without any victim interaction, the attacker interacts with the vulnerable Platform Security functionality.
  3. Successful exploitation results in takeover of OBIEE, with high confidentiality, integrity and availability impact.
  4. Because the scope is changed, the attack may significantly impact additional products. Oracle does not name those products, so this should not be treated as a confirmed inventory of vulnerable systems.

The specific requests involved are not disclosed. The public record therefore supports prioritization, but not a reliable exploit test or a precise attack signature.

Exploitation status

The reviewed Oracle and NVD records describe exploitability, not observed attacks. VulDB reports no public exploit, no specific threat actor is attributed, and a CISA KEV entry for this CVE was not established from the retrieved catalog material. Unconfirmed is not the same as absent. Separately, Oracle's advisory notes as general experience that attackers have exploited previously patched Oracle vulnerabilities on systems where customers had not applied available updates. That is not a claim about this CVE.

Patch information

Oracle fixed CVE-2026-114784 in its November 2026 Critical Security Patch Update, released on 17 November 2026. The CVE has its own row in the Oracle Analytics Risk Matrix of that advisory, with no other CVEs or extra notes sharing the row. One upstream summary placed it in the Fusion Middleware matrix, but the advisory itself lists it under Oracle Analytics. The Oracle Analytics section of this CSPU contains 29 new security patches, 9 of which are remotely exploitable without authentication. NVD published its entry the same day, sourced from Oracle, and links back to the CSPU advisory as the fix reference.

Obtaining the patch

  • The fix ships only as binary patches through My Oracle Support. No public commit or code diff exists, since the product is closed source.
  • The patch availability document for this product family is Oracle Analytics, Document ID CPU451. It lists exact patch numbers and installation steps for each affected release line (8.2.0.0.0 and 26.01.0.0.0).
  • Downloading requires an active Oracle support contract.
  • Public sources give no standalone fixed build number, so use CPU451 to confirm which patch matches your installed version.

Oracle's patch model

  • Cumulative: the November 2026 patches include fixes from earlier Critical Patch Updates and CSPUs. Applying the latest patch for your release line covers this CVE and anything missed previously, so there is no need to step through older advisories in order.
  • Supported versions only: CSPU fixes ship only for versions in Premier Support or Extended Support. For unsupported OBIEE releases, the path is to upgrade to a supported release (8.2.0.0.0 or 26.01.0.0.0) and then apply the patch.
  • Workarounds are not a fix: Oracle states that blocking network protocols or removing privileges does not correct the underlying problem. Blocking HTTP may temporarily reduce risk until patching, but Oracle warns such changes can break application functionality. Removing privileges offers little here because the flaw requires none (PR:N). Oracle urges customers to apply the patch as soon as possible, after testing on nonproduction systems.

Affected systems and versions

  • Vendor: Oracle Corporation
  • Product: Oracle Business Intelligence Enterprise Edition (Oracle Analytics)
  • Component: Platform Security
  • Affected supported versions: 8.2.0.0.0 and 26.01.0.0.0
  • Vulnerable configuration: any affected instance reachable by an attacker over HTTP. No authentication or user interaction is required.
  • Unsupported releases: Oracle does not test releases outside Premier or Extended Support for this flaw, but states that earlier versions are likely affected as well.

Oracle's analytics portfolio also includes Oracle Analytics Cloud (Oracle managed) and Oracle Analytics Server (customer managed). Those portfolio descriptions do not establish that every deployment model is affected. The confirmed exposure is the named product, component and versions above.

Vendor security history

Oracle runs quarterly Critical Patch Updates alongside monthly Critical Security Patch Updates. Its policy describes the monthly program as delivering timely fixes for critical issues, with quarterly CPUs rolling in earlier CSPU fixes. That establishes a remediation process, not an absence of serious vulnerabilities. Oracle also reports being named a Leader in the June 16, 2025 Gartner Magic Quadrant for Analytics and Business Intelligence Platforms, which speaks to market position rather than security effectiveness.

A useful, but unrelated, precedent is CVE-2025-61882 in Oracle EBS. CISA's KEV catalog describes an unauthenticated HTTP attack against the BI Publisher Integration component that can result in takeover of Oracle Concurrent Processing. CISA added it on October 6, 2025 and marks it as known to be used in ransomware campaigns. Google Threat Intelligence Group and Mandiant documented an associated extortion campaign by actors claiming affiliation with the CL0P brand, including successful data exfiltration in some cases and Oracle's emergency patch direction on October 4, 2025. Google did not formally attribute that activity to a tracked group and noted uncertainty about the exact vulnerability-to-exploit-chain mapping.

That case shows how consequential an unauthenticated takeover in an integrated Oracle enterprise product can be. It does not establish any technical or actor linkage to CVE-2026-114784, and nothing in the current record ties this OBIEE flaw to CL0P or any other group.

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