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-91574 Overview
CVE-2026-91574 is a vulnerability in the Oracle BI Publisher product of Oracle Analytics, specifically within the BI Publisher Security component. The flaw allows a low-privileged attacker with network access over HTTP to compromise confidentiality of data managed by Oracle BI Publisher. Successful exploitation grants unauthorized access to critical data or complete read access to all data accessible through Oracle BI Publisher. Oracle disclosed the issue as part of the October 2026 Critical Patch Update cycle.
Critical Impact
An authenticated attacker with low privileges can remotely exfiltrate critical business reporting data from affected Oracle BI Publisher deployments.
Affected Products
- Oracle BI Publisher 8.2.0.0.0
- Oracle BI Publisher 12.2.1.4.0
- Oracle BI Publisher 26.01.0.0.0
Discovery Timeline
- 2026-10-20 - CVE-2026-91574 published to NVD
- 2026-10-21 - Last updated in NVD database
Technical Details for CVE-2026-91574
Vulnerability Analysis
The vulnerability resides in the BI Publisher Security component of Oracle BI Publisher. An attacker only requires network access over HTTP and a low-privileged account to reach the exposed functionality. The scope remains unchanged, which means exploitation does not pivot into other security authorities. Impact is limited to confidentiality: the attacker can read sensitive report data, data model content, or connection metadata handled by BI Publisher. Integrity and availability of the BI Publisher service are not affected based on the published CVSS vector.
Oracle categorizes the issue as easily exploitable, meaning no complex preconditions or user interaction are required beyond holding a valid low-privileged session. The vulnerability is disclosed in the Oracle Security Alert October 2026.
Root Cause
Oracle has not published root-cause details beyond identifying the BI Publisher Security component. The nature of the component and the confidentiality-only impact are consistent with a broken access control or authorization bypass pattern, where an authenticated user can request data that should be restricted to higher-privileged roles.
Attack Vector
Exploitation occurs over the network via HTTP against the BI Publisher web interface or its APIs. The attacker must authenticate with low privileges, such as a standard reporting user, and then issue requests to functionality that fails to properly enforce authorization. No user interaction from administrators or other users is required.
No verified proof-of-concept code is publicly available at the time of publication. Technical details are described in prose only; refer to the Oracle Security Alert October 2026 for vendor guidance.
Detection Methods for CVE-2026-91574
Indicators of Compromise
- Unusual volumes of report downloads, data model queries, or scheduled job exports originating from low-privileged BI Publisher accounts.
- Access attempts from authenticated users to report paths, data sources, or administrative endpoints that fall outside their assigned role.
- HTTP requests to BI Publisher servlets or REST endpoints containing manipulated identifiers, path segments, or privilege parameters.
Detection Strategies
- Enable WebLogic and BI Publisher audit logging and forward records to a SIEM for correlation of authentication, authorization, and data access events.
- Baseline normal report access patterns per user and role, then alert on deviations such as cross-tenant access or sudden spikes in data retrieval.
- Inspect HTTP access logs for repeated 2xx responses to sensitive endpoints following prior 403 denials from the same session.
Monitoring Recommendations
- Review BI Publisher user and role assignments, focusing on accounts marked as low-privileged that still access sensitive report folders.
- Monitor outbound network egress from BI Publisher hosts for atypical data volumes that could indicate bulk extraction.
- Track application of the October 2026 Oracle Critical Patch Update across all BI Publisher instances and flag unpatched hosts.
How to Mitigate CVE-2026-91574
Immediate Actions Required
- Apply the fixes referenced in the Oracle Critical Patch Update of October 2026 to all affected BI Publisher versions 8.2.0.0.0, 12.2.1.4.0, and 26.01.0.0.0.
- Inventory all Oracle BI Publisher deployments, including those embedded in Oracle Analytics Server or Fusion Middleware stacks, and confirm patch status.
- Audit low-privileged BI Publisher accounts and remove any that are inactive, shared, or no longer required.
Patch Information
Oracle released patches for CVE-2026-91574 in the October 2026 Critical Patch Update. Administrators should obtain the appropriate patch for their BI Publisher release through My Oracle Support and apply it following Oracle's documented procedures for Fusion Middleware and Analytics components.
Workarounds
- Restrict network access to BI Publisher HTTP and HTTPS listeners to trusted internal networks and reverse proxies that enforce authentication.
- Enforce least privilege on BI Publisher roles so standard users cannot reach sensitive data models, reports, or administrative functions.
- Place a web application firewall in front of BI Publisher to inspect and rate-limit requests to data access endpoints until patches are deployed.
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

