PatchSiren

PatchSiren cyber security CVE debrief

CVE-2026-83310 Oracle Corporation CVE debrief

A vulnerability in Oracle BI Publisher of Oracle Analytics allows low-privileged attackers with network access via HTTP to compromise the product, potentially impacting additional products. Successful attacks require human interaction and can result in unauthorized data access or modification. The vulnerability affects versions 8.2.0.0.0, 12.2.1.4.0, and 26.01.0.0.0 of Oracle BI Publisher. Defenders should verify exposure, assess human interaction risks, and apply patches or mitigations promptly.

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

Who should care

Defenders responsible for Oracle BI Publisher deployments, security teams assessing data access risks, and IT staff managing software updates should be aware of this vulnerability and take necessary actions to verify exposure and apply mitigations.

Why it matters

CVE-2026-83310 is a high-severity vulnerability in Oracle BI Publisher that allows low-privileged attackers to compromise the product and potentially impact data. Defenders should verify exposure, assess human interaction risks, and apply patches or mitigations promptly.

  • Potential unauthorized data access or modification.
  • Required human interaction for successful attacks.
  • Possible impact on additional products beyond Oracle BI Publisher.
  • Need for prompt patching or mitigation to prevent exploitation.

Technical summary

The vulnerability in Oracle BI Publisher allows low-privileged attackers with network access via HTTP to compromise the product. Successful attacks require human interaction and can result in unauthorized creation, deletion, or modification access to critical data or all Oracle BI Publisher accessible data, as well as unauthorized access to critical data or complete access to all Oracle BI Publisher accessible data.

Defensive priority

Defenders should prioritize verifying exposure, assessing human interaction risks, and applying patches or mitigations.

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.
  • Assess human interaction risks and implement necessary mitigations.
  • Apply patches or updates provided by Oracle as soon as possible.
  • Monitor for potential unauthorized data access or modification.
  • 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.
  • Track exceptions, retest remediated assets, and close the item only after evidence is documented.

Evidence notes

The CVE record and NVD entry provide details on the vulnerability, affected versions, and potential impacts. However, additional information on exploitation or specific attacks is not available. The vulnerability has a CVSS score of 8.7 and is considered high-severity. Oracle BI Publisher deployments should be reviewed for exposure, and necessary mitigations should be applied. The CVE record was published on 2026-09-15T20:18:43.967Z and has not been modified since then. No additional information on exploitation or specific attacks is

Sources and references

Verified primary and authoritative sources

  • CVE-2026-83310 CVE Program record

    Publisher, destination, and source semantics verified

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

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

  • CVE-2026-83310 NVD vulnerability detail

    Publisher, destination, and source semantics verified

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

    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.