Security readout for executives and security teams
Plain-English summary
Oracle BI Publisher versions 8.2.0.0.0 and 12.2.1.4.0 contain a critical security weakness. An unauthenticated attacker who can reach the service over HTTP may take complete control, potentially exposing reports and data, enabling unauthorized changes, and disrupting availability.
Executive priority
Treat as an immediate remediation priority, especially for internet-facing or business-critical deployments. The combination of unauthenticated network access and potential full takeover creates material confidentiality, integrity, and availability risk. Confirm ownership, exposure, patch status, and monitoring promptly.
Technical view
CVE-2026-60173 is an unauthenticated, network-accessible vulnerability in Oracle BI Publisher's BI Platform Security component. Oracle assigns CVSS 3.1 score 9.8 and vector AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H. The record associates it with CWE-284, indicating improper access control, but provides no detailed root cause.
Likely exposure
Deployments running exactly the listed supported versions are affected when attackers can reach BI Publisher through HTTP. Internet-facing systems present the clearest risk, while internally accessible systems remain exposed to attackers with network footholds. The bundle does not identify affected configurations beyond product version and HTTP accessibility.
Exploitation context
The vulnerability reportedly requires no authentication, user interaction, or unusual attack complexity and may result in complete BI Publisher takeover. The supplied bundle says it is not in KEV and provides no evidence of active exploitation, public proof-of-concept code, or observed attacks.
Researcher notes
Public information in the supplied bundle is limited to affected versions, component, impact, CVSS vector, and CWE-284. It does not disclose the vulnerable endpoint, underlying code defect, indicators of compromise, patch identifier, or exploitation telemetry. Validation should remain defensive and follow Oracle guidance.
Mitigation direction
- Identify Oracle BI Publisher instances running versions 8.2.0.0.0 or 12.2.1.4.0.
- Review Oracle's July 2026 Critical Patch Update for the vendor-approved remediation.
- Apply Oracle-provided security updates under an expedited change process.
- Restrict HTTP access to trusted networks until remediation is confirmed.
- Monitor exposed instances for suspicious access and unauthorized administrative changes.
Validation and detection
- Inventory BI Publisher versions and confirm whether either affected release is deployed.
- Map all HTTP exposure, including internet-facing proxies, load balancers, and internal network paths.
- Confirm Oracle's applicable update is installed using vendor-supported version or patch records.
- Review authentication, access, and administrative logs for unexplained activity.
- Verify access restrictions prevent untrusted networks from reaching BI Publisher.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-284: Authorization and privilege behavior lookup
Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2026-60173 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Critical
- CVSS
- 9.8 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H3.95.9oracleVulnerability scoring details
Base CVSS 3.1 score
9.8CriticalVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- Oracle AdvisoryCVE reference, oracle · vendor-advisory
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Access Control
Improper Access Control represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.