PatchSiren cyber security CVE debrief
CVE-2026-83297 Oracle Corporation CVE debrief
A high-severity vulnerability exists in Oracle BI Publisher, allowing low-privileged attackers with network access via LDAP to compromise the system. Successful attacks can lead to unauthorized creation, deletion, or modification of critical data, as well as unauthorized access to critical or all accessible data. This vulnerability, tracked as CVE-2026-83297, affects Oracle BI Publisher versions 8.2.0.0.0, 12.2.1.4.0, and 26.01.0.0.0. The vulnerability has a CVSS 3.1 Base Score of 8.1, indicating high severity. Defenders should verify exposure, assess potential impact, and prioritize remediation to prevent unauthorized data access.
- Vendor
- Oracle Corporation
- Product
- Oracle BI Publisher
- CVSS
- HIGH 8.1
- 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 systems, particularly those with low-privileged network access via LDAP, should assess exposure and prioritize remediation to prevent unauthorized data access.
Why it matters
A high-severity vulnerability in Oracle BI Publisher allows low-privileged attackers to compromise the system and access critical data, requiring defenders to verify exposure, assess impact, and prioritize remediation.
- Potential unauthorized creation, deletion, or modification of critical data
- Potential unauthorized access to critical or all accessible data
- Need for verification of system versions and configurations
- Priority for applying remediation to prevent exploitation
Technical summary
The vulnerability exists in Oracle BI Publisher, specifically in the BI Platform Security component. Affected versions include 8.2.0.0.0, 12.2.1.4.0, and 26.01.0.0.0. The CVSS 3.1 Base Score is 8.1, indicating high severity. The vulnerability allows low-privileged attackers with network access via LDAP to compromise the system. 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 access to critical data or complete access to all Oracle BI Publisher accessible data.
Defensive priority
Defenders should prioritize verifying exposure, assessing potential impact, and applying remediation to prevent unauthorized data access.
Recommended defensive actions
- Verify exposure by checking system versions and configurations
- Assess potential impact on critical data and business operations
- Apply remediation to prevent unauthorized data access
- Monitor system activity for suspicious behavior
- 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, victims, or specific business impacts is not available in the supplied corpus.
Sources and references
Verified primary and authoritative sources
-
CVE-2026-83297 CVE Program record
Publisher, destination, and source semantics verified
URL: https://www.cve.org/CVERecord?id=CVE-2026-83297
CVE Program - Official CVE Program record with source-provided CVE metadata.
-
CVE-2026-83297 NVD vulnerability detail
Publisher, destination, and source semantics verified
URL: https://nvd.nist.gov/vuln/detail/CVE-2026-83297
NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.
Supplemental references
-
Source reference
Unverified legacy reference
URL: https://www.oracle.com/security-alerts/cspusep2026.html
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.