Oracle BI Publisher is a widely deployed enterprise analytics product; an exploitable network SOAP vulnerability (CVSS 8.5) allowing data modification/unauthorized access can disrupt reporting and analytics across organizations.
CVE-2026-83303
Oracle BI Publisher SOAP flaw allows low-privileged remote attackers to modify/read BI data (CVSS 8.5).
Is CVE-2026-83303 being exploited?
Not confirmed. CVE-2026-83303 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked.
How severe is CVE-2026-83303?
CVE-2026-83303 is rated High with a CVSS score of 8.5. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-83303?
Not known from our data. No patch reference has been recorded for CVE-2026-83303, which is not the same as no patch existing — a fix may have shipped without a tagged reference, or after this record was written. The vendor advisory is the only authority on whether a fix exists, and mitigations may be available regardless.
What does CVE-2026-83303 affect?
CVE-2026-83303 affects Oracle BI Publisher 8.2.0.0.0, Oracle BI Publisher 12.2.1.4.0, Oracle BI Publisher 26.01.0.0.0, Oracle Analytics (BI Platform). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-83303?
Apply vendor patch when available; restrict SOAP/network access and monitor BI Publisher logs.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Low-privileged remote attacker via SOAP can create, delete or modify BI Publisher data and read subsets of data; scope change may affect additional Oracle products.
Immediate action required
- affected8.2.0.0.0
- affected12.2.1.4.0
- affected26.01.0.0.0
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.