PatchSiren

PatchSiren cyber security CVE debrief

CVE-2026-83303 Oracle Corporation CVE debrief

A high-severity vulnerability exists in Oracle BI Publisher, allowing low-privileged attackers with network access via SOAP to compromise the product. Successful attacks can result in unauthorized creation, deletion, or modification access to critical data or all Oracle BI Publisher accessible data, as well as unauthorized read access to a subset of Oracle BI Publisher accessible data.

Vendor
Oracle Corporation
Product
Oracle BI Publisher
CVSS
HIGH 8.5
CISA KEV
Not listed in stored evidence
Original CVE published
2026-09-15
Original CVE updated
2026-09-22
Advisory published
2026-09-15
Advisory updated
2026-09-22

Who should care

Defenders responsible for Oracle BI Publisher systems, security teams, IT administrators, and vulnerability management teams should assess exposure and apply patches or updates to prevent exploitation. This includes operators managing Oracle BI Publisher deployments and security personnel responsible for monitoring and defending against potential attacks.

Why it matters

A high-severity vulnerability in Oracle BI Publisher requires defenders to verify exposure and apply patches to prevent potential unauthorized access and data manipulation.

  • Potential unauthorized access to critical data or all Oracle BI Publisher accessible data
  • Potential unauthorized creation, deletion, or modification of critical data
  • Potential read access to a subset of Oracle BI Publisher accessible data
  • Verification of exposure and patch application is required

Technical summary

The vulnerability exists in the Oracle BI Publisher product of Oracle Analytics (component: BI Platform Security). It allows low-privileged attackers with network access via SOAP to compromise Oracle BI Publisher. Successful attacks can result in unauthorized creation, deletion, or modification access to critical data or all Oracle BI Publisher accessible data, as well as unauthorized read access to a subset of Oracle BI Publisher accessible data. The CVSS 3.1 Base Score is 8.5 (Confidentiality and Integrity impacts).

Defensive priority

Defenders should prioritize verifying exposure and applying patches, as the vulnerability has a high CVSS score of 8.5 and can significantly impact additional products.

Recommended defensive actions

  • Verify exposure by checking if Oracle BI Publisher versions 8.2.0.0.0, 12.2.1.4.0, or 26.01.0.0.0 are in use
  • Apply patches or updates provided by Oracle to fix the vulnerability
  • Monitor network access to Oracle BI Publisher for suspicious activity
  • Review and update access controls to prevent low-privileged attackers from exploiting the vulnerability
  • Track exceptions and retest remediated assets
  • Review compensating controls for exposed systems while remediation is scheduled and verified
  • Check relevant monitoring, detection, and logs for exposed assets that need extra review

Evidence notes

The vulnerability is described in the CVE record and NVD detail page. Oracle has provided a security alert for this vulnerability. Defenders should verify exposure by checking if Oracle BI Publisher versions 8.2.0.0.0, 12.2.1.4.0, or 26.01.0.0.0 are in use and apply patches or updates provided by Oracle to fix the vulnerability. The evidence is limited to public sources and may not reflect all affected systems or potential impacts.

Sources and references

Verified primary and authoritative sources

  • CVE-2026-83303 CVE Program record

    Publisher, destination, and source semantics verified

    URL: https://www.cve.org/CVERecord?id=CVE-2026-83303

    CVE Program - Official CVE Program record with source-provided CVE metadata.

  • CVE-2026-83303 NVD vulnerability detail

    Publisher, destination, and source semantics verified

    URL: https://nvd.nist.gov/vuln/detail/CVE-2026-83303

    NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.

Supplemental references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.