Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessObtain account with DBMS_AW privilege
-
DeliveryConnect over Oracle Net
-
ExploitSend crafted OLAP request
-
ExecutionExploit OLAP component flaw
-
ImpactFull takeover of Oracle OLAP
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A06:2025 - Insecure Design
ASVS 5.0
V8 - Authorization Least privilege enforcement
MITRE ATT&CK
1 technique across 1 tactic: Privilege Escalation The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires the attacker to possess a valid Oracle Database account that has been granted the DBMS_AW privilege, and network reachability to the database listener over Oracle Net (default TNS, typically TCP 1521). No user interaction is required and attack complexity is low. The key limiting factor is the DBMS_AW privilege prerequisite (PR:L) - environments that tightly restrict this privilege and limit network exposure of the Oracle Net listener materially reduce exposure; this is not remotely exploitable by fully unauthenticated attackers. Affected versions are 19.3-19.32, 21.3-21.23, and 23.4.0-23.26.3. |
| Impact | This is a genuinely high-priority vulnerability but not an emergency. The CVSS 3.1 vector (AV:N/AC:L/PR:L/UI:N) describes a low-complexity, network-reachable attack over Oracle Net that requires only low privileges - specifically an account holding the DBMS_AW privilege - and yields full C:H/I:H/A:H impact (complete OLAP component takeover). This combination of easy exploitation plus total impact is why Oracle rates it 8.8. However, the mitigating reality is PR:L: the attacker must already hold a valid database account with the DBMS_AW privilege, so this is a privilege-escalation/post-authentication issue, not a remote-unauthenticated breach. No EPSS score is provided in the input, so exploitation probability cannot be quantified. There is no CISA KEV listing and no public proof-of-concept referenced, so there is no public exploit identified at time of analysis - the only reference is Oracle's October 2026 Critical Patch Update advisory. SSVC framing: exploitation status is 'none' observed, technical impact is 'total', and automatability is low because valid credentials/privileges are a prerequisite. Net: prioritize patching for any database where untrusted or numerous users hold DBMS_AW, but the authentication prerequisite makes mass, widespread exploitation less likely than a PR:N network flaw would be. |
| Exploit ScenarioDerived | An attacker who already holds a low-privileged Oracle Database account carrying the DBMS_AW privilege connects to the database over Oracle Net and sends crafted requests to the OLAP component, leveraging the flaw to fully compromise OLAP (read/modify data and disrupt availability). Because CVSS indicates AC:L, the attack is reliable once the privilege is held; no user interaction is needed. No public proof-of-concept is referenced, so exploitation would require independent development. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 20, 2026
Oracle Database's OLAP component in versions 19.3-19.32, 21.3-21.23, and 23.4.0-23.26.3 can be compromised by an authenticated, low-privileged database user who holds the DBMS_AW privilege and can reach the Oracle Net listener; successful exploitation can result in takeover of Oracle OLAP with high confidentiality, integrity, and availability impact (CVSS 8.8). The attack requires network access via Oracle Net but no user interaction, and the main exposure control is limiting who receives DBMS_AW and how broadly the listener is reachable. No public exploit code or confirmed active exploitation was identified at time of analysis.
RemediationAI
Patch available per vendor advisory: apply the Oracle Critical Patch Update for October 2026 (https://www.oracle.com/security-alerts/cpuoct2026.html); the input does not provide a more specific fix version than the CPU release, so confirm the patched build for your supported 19.x, 21.x, or 23.x database from Oracle's advisory. Until patching is complete, restrict the DBMS_AW privilege to only accounts that genuinely require Oracle OLAP analytic workspace administration and review existing grants, accepting that this may break legitimate OLAP workflows; and limit network access to the Oracle Net listener (typically TCP 1521) through firewall rules, listener ACLs, or database network ACLs, accepting that this may disrupt application connectivity that depends on remote database access. Monitor for unexpected grants or use of DBMS_AW and unusual Oracle Net sessions as compensating detection while the patch is staged.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The flaw resides in Oracle OLAP, the analytic engine embedded in Oracle Database Server, and is reached over Oracle Net (typically TNS on TCP 1521) by a database account granted DBMS_AW, the Oracle OLAP analytic workspace administration privilege. The CVSS 3.1 vector AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H indicates low attack complexity and no user interaction, but the PR:L prerequisite means the attacker must already hold a valid database login with DBMS_AW rather than being fully unauthenticated. No CWE is assigned and Oracle's advisory does not publicly detail the underlying coding defect, so the precise root-cause class cannot be confirmed from available data; the impacted releases are 19.3-19.32, 21.3-21.23, and 23.4.0-23.26.3. The October 2026 Oracle Critical Patch Update is the referenced vendor advisory.
Know when the next one hits your stack
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
AV:N and AC:L because exploitation is over Oracle Net and described as easy; PR:L because the DBMS_AW database privilege is required; full C/I/A takeover of OLAP.
Primary rating from Vendor (oracle).
CVSS VectorVendor: oracle
DescriptionCVE.org
Vulnerability in the Oracle OLAP component of Oracle Database Server. Supported versions that are affected are 19.3-19.32, 21.3-21.23 and 23.4.0-23.26.3. Easily exploitable vulnerability allows low privileged attacker having DBMS_AW privilege with network access via Oracle Net to compromise Oracle OLAP. Successful attacks of this vulnerability can result in takeover of Oracle OLAP. CVSS 3.1 Base Score 8.8 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H).
Executive ViewAI
Oracle Database's OLAP analytics component, across the 19c, 21c and 23ai release streams (19.3-19.32, 21.3-21.23, 23.4.0-23.26.3), is exposed to a high-severity flaw (CVSS 8.8) that could allow a database account holding OLAP privileges to take over the component and read, alter or disrupt the data it serves. Because no vendor-released patch is identified at time of analysis, leadership should treat this as a privileged-access and network-exposure governance issue affecting the teams that own financial reporting, planning and warehouse workloads on these databases. Impact is contained to accounts already granted OLAP privileges and to networks that can reach the Oracle Net listener, making entitlement reduction and listener hardening the fastest levers available.
No vendor-released patch identified at time of analysis. Interim mitigations: revoke DBMS_AW from all accounts without a documented OLAP requirement and route any new grants through formal approval; restrict reachability of the Oracle Net listener with network ACLs, firewalls or listener-level access control so only trusted application tiers and administrative hosts can connect; disable the Oracle OLAP option on instances that do not require it; enable and monitor auditing for OLAP activity, privilege grants and anomalous listener connections; and apply strict least privilege to database accounts that must retain OLAP access.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Privilege escalation occurs when an attacker leverages flaws in access control mechanisms to gain permissions beyond what they were originally granted.
EUVD-2026-106785
GHSA-79vg-6vp5-m284
NVD
CVE.org
EPSS
Exploit-DB