Oracle Analytics patches 50 vulnerabilities including four critical flaws
Free public brief. The indicators, the detections with Splunk SPL already written (plus Elastic and KQL where they apply), and a Slack alert the next time this touches a vendor you run are in the app — free account, no card.
Oracle fixes 50 flaws in Analytics products; four critical, eight exploitable without authentication, requiring immediate patching.
Oracle has issued patches for 50 vulnerabilities across its Analytics product line, including Oracle Business Intelligence Enterprise Edition and Oracle BI Publisher. Four vulnerabilities carry critical severity ratings (CVSS 9.1–9.9), with three scoring 9.8 or higher. Eight flaws can be exploited remotely without authentication over HTTP, potentially allowing complete system takeover. The most severe issues are CVE-2026-83269 (CVSS 9.8, unauthenticated remote) and CVE-2026-83283 (CVSS 9.8, unauthenticated remote), both in Platform Security components, and CVE-2026-83282 (CVSS 9.9, requires low privilege). The remaining 46 vulnerabilities range from CVSS 7.0 to 8.9 and may require user interaction or prior access. Successful exploitation can lead to unauthorized access to sensitive data, data modification or deletion, complete component takeover, and denial of service. NCSC-NL advises prioritizing patches for the critical vulnerabilities immediately.
Mentioned in this report
Detection guidance
WebLogic Java Server Spawning Command Shell or Download Utility
Detects the Oracle WebLogic Java process, which hosts Oracle BI and BI Publisher, spawning a shell or download utility. This is a typical post-exploitation sign of unauthenticated remote exploitation of a public-facing Oracle Analytics component. Auto-generated starting point — validate and tune in your environment before deploying. IOC matches can false-positive on shared infrastructure and decay as adversary infrastructure rotates.
title: WebLogic Java Server Spawning Command Shell or Download Utility
id: 21a939e2-ead7-5a3e-8e63-a1b7eabac600
status: experimental
description: Detects a WebLogic-hosted Java process (the platform for Oracle BI Enterprise
Edition and BI Publisher) spawning cmd, PowerShell, or common LOLBins for download
and execution. This is typical post-exploitation behaviour after remote exploitation
of a public-facing Oracle Analytics component. Generalises on the parent/child relation,
not on any specific CVE or payload.
tags:
- attack.initial-access
- attack.t1190
- attack.execution
logsource:
category: process_creation
product: windows
detection:
selection_parent:
ParentImage|endswith: \java.exe
ParentCommandLine|contains:
- weblogic.Server
- weblogic.Name
- bifoundation
- OracleBI
selection_child:
Image|endswith:
- \cmd.exe
- \powershell.exe
- \pwsh.exe
- \certutil.exe
- \bitsadmin.exe
- \mshta.exe
- \wscript.exe
- \cscript.exe
- \rundll32.exe
- \regsvr32.exe
filter_admin_scripts:
CommandLine|contains:
- startWebLogic
- stopWebLogic
- nmstart
condition: selection_parent and selection_child and not filter_admin_scripts
falsepositives:
- Oracle BI or WebLogic administrative and start/stop scripts invoked through cmd.exe
by the Java process
- Custom BI Publisher scheduled jobs that deliberately call batch scripts
level: high
author: Vorant
references:
- https://advisories.ncsc.nl/2026/ncsc-2026-0379.html
Behavioural rules are generated from public reporting — validate in your environment before deploying.
Source reporting: https://advisories.ncsc.nl/2026/ncsc-2026-0379.html
What this brief leaves out
This page is the free tier: the write-up, the severity, the names. In the app the same report carries its extracted indicators, its detections (Splunk SPL already written, plus Elastic and Microsoft KQL where they apply), the actors and CVEs it names as live profiles, and the vendor research on the same campaign — the primary source the news paraphrased, cited and read directly.
It sits in a corpus of 13,854 reports from 146 sources, 616 of them written in the last seven days, and it grows through the day.
A new account starts with three days of all of it, no card, then keeps the government and CERT reporting free. Name the vendors you run and Slack hears about the reports that touch them — about forty a week that are yours, not the four hundred that are not.
Create a free account What it costs