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-91528 Overview
CVE-2026-91528 affects Oracle BI Publisher within the Oracle Analytics product family, specifically in the BI Platform Security component. The vulnerability exists in version 12.2.1.4.0 and allows a low-privileged attacker with network access over HTTPS to compromise the application. Successful exploitation results in unauthorized read access to a subset of Oracle BI Publisher accessible data. The flaw impacts confidentiality only, with no integrity or availability consequences.
Critical Impact
Authenticated remote attackers can read a subset of data stored or processed by Oracle BI Publisher, exposing potentially sensitive reporting data and business intelligence content.
Affected Products
- Oracle BI Publisher 12.2.1.4.0
- Oracle Analytics (BI Platform Security component)
- Deployments exposing BI Publisher over HTTPS to authenticated users
Discovery Timeline
- 2026-10-20 - CVE-2026-91528 published to the National Vulnerability Database (NVD)
- 2026-10-21 - Last updated in NVD
- October 2026 - Addressed in the Oracle Critical Patch Update, October 2026
Technical Details for CVE-2026-91528
Vulnerability Analysis
The weakness resides in the BI Platform Security component that enforces access control within Oracle BI Publisher. An authenticated user with low privileges can issue crafted HTTPS requests to the server and retrieve data they are not authorized to view. Because the attack vector is Network and the required user interaction is None, exploitation can be scripted against any reachable instance where the attacker holds valid credentials.
The disclosed data is described by Oracle as a subset of BI Publisher accessible data. In practice, BI Publisher hosts report templates, data models, and query output that may contain financial, HR, or operational records. Information disclosure in this component therefore has direct business impact even without integrity or availability loss.
Root Cause
Oracle has not published root cause details beyond the component identification. The flaw is consistent with insufficient authorization checks on protected resources within the BI Platform Security layer, where privilege boundaries between report consumers and privileged data are not enforced for all request paths.
Attack Vector
An attacker needs network reachability to the BI Publisher HTTPS endpoint and valid low-privileged credentials. No user interaction and no elevated privileges are required. The attacker sends crafted HTTPS requests to BI Publisher endpoints that return data outside the attacker's authorization scope. No public proof-of-concept, exploit module, or evidence of in-the-wild exploitation is referenced in the advisory. The EPSS probability is 0.215% (percentile 11.2), indicating low near-term exploitation likelihood.
// No verified public proof-of-concept is available.
// Refer to the Oracle Critical Patch Update for technical remediation details.
Detection Methods for CVE-2026-91528
Indicators of Compromise
- Authenticated BI Publisher sessions issuing unusual volumes of report or data-model retrieval requests from a single low-privileged account
- HTTPS requests to BI Publisher REST or SOAP endpoints returning data outside the user's assigned reports or folders
- Access patterns targeting BI Platform Security endpoints from accounts that historically never queried those paths
Detection Strategies
- Review BI Publisher audit logs for user accounts accessing data models, reports, or data sources outside their role assignments
- Correlate web server access logs with application-level authorization decisions to surface requests that returned data despite low role membership
- Alert on BI Publisher API calls that enumerate reports, folders, or data sources at a rate inconsistent with normal user behavior
Monitoring Recommendations
- Enable Oracle BI Publisher auditing and forward logs to a centralized SIEM for retention and correlation
- Baseline normal report access per user and alert on deviations in object counts, request rates, or payload sizes
- Monitor for new or anomalous service accounts authenticating to BI Publisher over HTTPS
How to Mitigate CVE-2026-91528
Immediate Actions Required
- Apply the fixes delivered in the Oracle Critical Patch Update, October 2026 to Oracle BI Publisher 12.2.1.4.0
- Inventory all BI Publisher deployments and confirm patch coverage across production, staging, and disaster-recovery environments
- Rotate credentials for low-privileged BI Publisher accounts, especially shared or service accounts
Patch Information
Oracle addressed CVE-2026-91528 in the October 2026 Critical Patch Update. Administrators should review the advisory for the specific patch identifiers and apply them to all affected 12.2.1.4.0 instances. Oracle generally requires patches to be installed in the order published; verify prerequisites before deployment.
Workarounds
- Restrict network access to BI Publisher HTTPS endpoints using firewall rules, VPN gating, or reverse proxy allowlists
- Reduce standing privileges by removing unneeded BI Publisher user accounts and tightening role assignments
- Place BI Publisher behind a web application firewall and log anomalous access to report and data-model APIs until patching is complete
# Example: restrict BI Publisher access at the network layer
# Replace the source range with your trusted internal subnet
iptables -A INPUT -p tcp --dport 9502 -s 10.0.0.0/8 -j ACCEPT
iptables -A INPUT -p tcp --dport 9502 -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

