How do I check whether I am affected by CVE-2026-91563?

Check the version: SELECT banner_full FROM v$version, or opatch lspatches, and compare with the affected ranges. Check whether OLAP is installed: SELECT comp_id, status FROM dba_registry WHERE comp_id='OLAP'. Check who holds the privilege: SELECT grantee FROM dba_tab_privs WHERE table_name='DBMS_AW' (also check dba_role_privs for roles granting it). If OLAP is not installed and nobody has DBMS_AW, exposure is likely low, though Oracle's patch doc is the authority.

What is the fix for CVE-2026-91563?

Apply the Oracle October 2026 Critical Patch Update for your release (via My Oracle Support patch availability document for Database); this means moving past 19.32, 21.23 and 23.26.3. Exact RU numbers not read. Workaround from Oracle and Armis: revoke DBMS_AW (and EXECUTE on it) from accounts that do not need it; this disables OLAP analytic workspace use for them.

Who is not affected by CVE-2026-91563?

Not affected if: auth-required, managed-hosting, olap-not-installed, unknown.

Live › vulnerability › CVE-2026-91563

Go to dashboard

high8.8Package

Oracle Database OLAP: low-privilege user with DBMS_AW can take over

Oracle Database Server OLAP component flaw (Oct 2026 CPU). A low-privileged user holding the DBMS_AW privilege can take over Oracle OLAP over Oracle Net. CVSS 8.8, with high confidentiality, integrity and availability impact. Affects 19.3-19.32, 21.3-21.23 and 23.4.0-23.26.3.

Summary written from the sources below. Check the originals before acting.

CVSS 3.x

8.8

high

scored by [email protected]

known so far5 of 6

missing: exploitation

First public: Oct 20, 2026 UTC
Last modified: Oct 23, 2026
Status: open
Known exploitation: None reported
Public exploit: None on GitHub
EPSS: not scored

First seen by InfraStack 2026-10-23 21:57 UTC. All times on this page are UTC.

Why it is high, and not just CVSS

Likelihood → · Impact ↓

critical

high

medium

high

medium

low

medium

low

Exploited: No reports yet.
Needs login: Yes.
Needs a special setup: Not known from the sources.
Reachable from: network.
Worst case: Attacker takes over the OLAP component and reads or changes its data.
CVSS said: 8.8. The facts above say medium; we keep the sources' high until an analyst looks.

Who is affected

1 product

Know the next one before it finds you.

Add to Slack

Live › vulnerability › CVE-2026-91563

Go to dashboard

high8.8Package

Oracle Database OLAP: low-privilege user with DBMS_AW can take over

Summary written from the sources below. Check the originals before acting.

CVSS 3.x

8.8

high

scored by [email protected]

known so far5 of 6

missing: exploitation

First public: Oct 20, 2026 UTC
Last modified: Oct 23, 2026
Status: open
Known exploitation: None reported
Public exploit: None on GitHub
EPSS: not scored

First seen by InfraStack 2026-10-23 21:57 UTC. All times on this page are UTC.

Why it is high, and not just CVSS

Likelihood → · Impact ↓

critical

high

medium

high

medium

low

medium

low

Exploited: No reports yet.
Needs login: Yes.
Needs a special setup: Not known from the sources.
Reachable from: network.
Worst case: Attacker takes over the OLAP component and reads or changes its data.
CVSS said: 8.8. The facts above say medium; we keep the sources' high until an analyst looks.

Who is affected

1 product

Know the next one before it finds you.

Add to Slack

Oracle Database OLAP: low-privilege user with DBMS_AW can take over

Why it is high, and not just CVSS

Who is affected

Know the next one before it finds you.

Oracle Database OLAP: low-privilege user with DBMS_AW can take over

Why it is high, and not just CVSS

Who is affected

Know the next one before it finds you.

How to check

The fix

Who had it, and when

What the sources say, verbatim

Sources