Summary
CVE-2026-83305 is a high-severity, unauthenticated vulnerability in the BI Platform Security component of Oracle BI Publisher (part of Oracle Analytics). An attacker with only network access via HTTP can compromise the application without any credentials or user interaction, potentially reading, modifying, or deleting BI Publisher data and disrupting service availability. Oracle rates this vulnerability CVSS 3.1 8.6 (High) and disclosed it in its September 2026 Critical Patch Update.
Technical details
- Root cause: A flaw in the BI Platform Security component of Oracle BI Publisher that fails to properly enforce authentication/authorization controls, as described in Oracle’s official CVE record.
- Trigger conditions: Exploitable remotely over HTTP with no authentication, no privileges, and no user interaction required — Oracle classifies it as "easily exploitable."
- Attack vector: Network (AV:N), low attack complexity (AC:L), no privileges required (PR:N), no user interaction (UI:N), scope unchanged (S:U).
- Impact: Successful exploitation can result in unauthorized access to critical data or complete access to all data accessible to BI Publisher, unauthorized update/insert/delete of some BI Publisher data, and a partial denial of service (partial DoS) of the application.
Affected software
- Oracle BI Publisher 8.2.0.0.0
- Oracle BI Publisher 12.2.1.4.0
- Oracle BI Publisher 26.01.0.0.0
Severity
- CVSS v3.1 Base Score: 8.6 (High)
- Vector:
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:L - Impact breakdown: Confidentiality: High, Integrity: Low, Availability: Low
Mitigation and recommended actions
- Immediate: Apply the Oracle Critical Patch Update for September 2026, which addresses CVE-2026-83305 for all listed affected BI Publisher versions (8.2.0.0.0, 12.2.1.4.0, 26.01.0.0.0). Oracle strongly recommends applying the fixes without delay, as this vulnerability may be remotely exploitable without authentication.
- If patching cannot be performed immediately: Restrict network exposure of Oracle BI Publisher — ensure it is not directly reachable from the public internet, place it behind a properly configured firewall/VPN or reverse proxy that limits HTTP access to trusted networks/users, and monitor access logs for anomalous unauthenticated requests until the patch can be applied.

