Automated Threat Modeling

Overview of CVE-2026-91533: Unauthenticated Data Exposure in the Oracle Access Manager Authentication Engine

A brief summary of CVE-2026-91533, a CVSS 8.2 flaw in the Oracle Access Manager Authentication Engine that lets an unauthenticated HTTP attacker read critical data and make limited changes. We cover affected versions, the November 2026 CSPU patch details, and what remains undisclosed.

CVE Analysis

7 min read

Gaurav Sarraf
Gaurav Sarraf

2026-11-17

Overview of CVE-2026-91533: Unauthenticated Data Exposure in the Oracle Access Manager Authentication Engine

Introduction

Oracle's November 2026 Critical Security Patch Update fixes a flaw in the Oracle Access Manager Authentication Engine that lets an unauthenticated attacker with HTTP access read critical data handled by the product and make limited changes to it. Access Manager sits in front of enterprise applications as the layer that decides who gets authenticated, so a defect in its authentication component is worth scheduling promptly, even though no exploitation has been reported so far.

The CVE data feed lists the vendor as Unknown, but the vendor is Oracle Corporation and the product is part of Oracle Fusion Middleware. Oracle's documentation describes Access Manager as a single sign-on system in which administrators define authentication and authorization policies for protected resources, with agents that filter HTTP requests to enforce those policies. That role in application access control is why we treat this as a security infrastructure issue rather than an isolated application bug.

Technical information

What Oracle has disclosed

Oracle's risk matrix for the November 2026 CSPU identifies the vulnerable component as the Authentication Engine of Oracle Access Manager, in supported versions 12.2.1.4.0 and 14.1.2.1.0. Oracle describes it as an easily exploitable vulnerability that allows an unauthenticated attacker with network access via HTTP to compromise Oracle Access Manager. The CVE record and NVD both show publication on 17 November 2026. The NVD score is attributed to Oracle, and NVD has not yet provided its own assessment.

The published vector is:

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N

Reading it against the FIRST CVSS v3.1 specification:

  • Attack Vector: Network (AV:N). Reachable over HTTP.
  • Attack Complexity: Low (AC:L). Oracle calls it easily exploitable.
  • Privileges Required: None (PR:N). No credentials are needed.
  • User Interaction: None (UI:N). No victim action is required.
  • Scope: Unchanged (S:U).
  • Confidentiality: High (C:H). Unauthorized access to critical data or complete access to all Oracle Access Manager accessible data.
  • Integrity: Low (I:L). Unauthorized update, insert or delete access to some Oracle Access Manager accessible data.
  • Availability: None (A:N).

The dominant concern is disclosure, with a narrower integrity impact. That impact has a boundary. The record speaks of Oracle Access Manager accessible data, and it does not state that every application protected by Access Manager becomes accessible. The base score also describes only intrinsic characteristics. FIRST keeps those separate from temporal factors such as exploit availability.

Root cause: what is and is not known

Access Manager is closed source, and Oracle has not published a vulnerable URL, request format, parameter, affected function, exploit sequence or description of the implementation defect. VulDB likewise lists the affected function and technical details as unknown. As a result, a reproducible exploitation method cannot be described from public evidence.

Secondary sources classify the bug differently:

  • VulDB maps it to CWE-285, Improper Authorization.
  • TheHackerWire labels it an authentication bypass.
  • NVD has no populated CWE entry.

Oracle confirms neither label, so we treat them as secondary mappings rather than an established root cause. What Oracle's description does support is that the fix corrects how the Authentication Engine handles unauthenticated requests. Nothing more specific about the code change is public.

Attack flow, as far as the disclosure allows

Based only on the published prerequisites and impacts:

  1. The attacker needs network reachability to an affected Access Manager deployment over HTTP.
  2. No account, session or credentials are required, and no user has to click or open anything.
  3. The attacker sends requests that reach the Authentication Engine. The specific request content is undisclosed.
  4. On success, the attacker can read critical data or all data accessible to Access Manager, and can update, insert or delete some of that data.

Oracle's description does not establish any of the following for this CVE: remote code execution, server takeover, an exploit chain, denial of service, or compromise of every connected application.

Exploitation status

As of 18 November 2026, the reviewed sources do not establish active exploitation. Rapid7 reports a CISA KEV status of false. TheHackerWire reports it is not in KEV, that no public exploit code has been confirmed, and that no ransomware campaign is known. VulDB reports no available exploit. No threat actor is attributed, and no indicators of compromise or exploit payloads have been published. These reflect available reporting and do not prove that no private exploit exists.

Patch information

Oracle fixed CVE-2026-91533 in its November 2026 Critical Security Patch Update (CSPU), released on 17 November 2026. Access Manager is closed source, so there is no public commit or diff. Everything below comes from Oracle's advisory and its machine-readable CSAF record.

What Oracle shipped

  • Product / component: Oracle Access Manager, Authentication Engine
  • Protocol: HTTP
  • Remotely exploitable without authentication: Yes
  • CVSS 3.1: 8.2
  • Versions covered by the fix: 12.2.1.4.0 and 14.1.2.1.0
  • Oracle Bug ID: 39284916

The CSAF entry sets the remediation category to vendor_fix for both affected product IDs, so this is a code fix rather than a configuration workaround. The details field states the fix is available to "Oracle customers with valid support contracts". Use Bug ID 39284916 to verify that a downloaded OAM patch, or the bug list in an installed patch README, actually contains this fix.

Where to get it

The advisory's Patch Availability Document for Fusion Middleware is My Oracle Support document CPU450, which lists the OAM patch numbers for each release along with installation steps. For the full history of current and earlier Fusion Middleware patches, Oracle points to MOS Doc ID KA1182. Both require a My Oracle Support login.

How the CSPU model affects deployment

CSPUs are a smaller, targeted companion to Oracle's quarterly cumulative Critical Patch Updates. This fix arrived mid-cycle rather than in the October 2026 CPU, which has two practical consequences:

  1. Install on top of a current baseline. A CSPU is a focused set of fixes, not a full rollup. Confirm the OAM home is at the latest quarterly CPU level, then apply the CSPU patch from CPU450.
  2. Only supported releases are covered. Oracle provides CSPU patches only for versions under Premier or Extended Support. If you run an OAM release other than 12.2.1.4.0 or 14.1.2.1.0, there is no patch to install. Upgrade to a supported release first.

The same Fusion Middleware matrix lists many other OAM CVEs, including CVE-2026-91498, CVE-2026-91500, CVE-2026-91507, CVE-2026-91509, CVE-2026-91510, CVE-2026-91516, CVE-2026-91522, CVE-2026-91531, CVE-2026-91540, CVE-2026-91543, CVE-2026-91564, CVE-2026-91671 and CVE-2026-114835. Many are also in the Authentication Engine. They all ship through the same CPU450 document, so plan to deploy the full November OAM patch rather than trying to isolate the fix for CVE-2026-91533.

Interim containment

If patching must wait, Oracle's advisory notes that blocking the network protocol an attack requires may reduce risk until patches are applied. Oracle is explicit that this can break application functionality, does not correct the underlying defect and is not a long-term solution, and it recommends testing such changes on nonproduction systems first.

Affected systems and versions

  • Oracle Access Manager 12.2.1.4.0 (Oracle Fusion Middleware), Authentication Engine component
  • Oracle Access Manager 14.1.2.1.0 (Oracle Fusion Middleware), Authentication Engine component

One upstream report listed 14.1.2.0.0 as affected. Oracle's advisory and CSAF data both name 14.1.2.1.0, so we use the Oracle values. The vulnerable configuration is any deployment of these versions whose Authentication Engine is reachable over HTTP by an attacker. No authentication or user interaction is needed. Releases outside Premier or Extended Support do not receive a CSPU patch and need an upgrade to a supported release.

Vendor security history

Oracle's documented remediation model uses quarterly Critical Patch Updates as the main vehicle for backporting security fixes to on-premises products, available to customers with valid support contracts. Oracle also reserves the ability to issue security alerts, patches or workarounds outside that schedule for particularly critical vulnerabilities or reported active exploitation. Oracle notes that updates are cumulative for many products, though not necessarily every product or package, and advises reviewing earlier patch advisories.

Access Manager has a notable prior incident. On 30 November 2022, Belgium's Centre for Cybersecurity warned that CVE-2021-35587, an unauthenticated HTTP vulnerability in the Access Manager OpenSSO component, was being actively exploited and could allow privileged user creation, lateral movement or arbitrary code execution. The CCB recommended patching with the highest priority after thorough testing.

That history shows Access Manager has been targeted in practice. It does not, however, tell us anything about the mechanism, actors or consequences of CVE-2026-91533, which affects a different component and has narrower stated impacts (no availability impact and no code execution in Oracle's description).

References

Detect & fix
what others miss

Works with
  • GitHub
  • GitLab
  • Bitbucket
  • Azure DevOps Services
  • Gerrit
  • CVS
  • Jira
  • Linear
  • Slack
  • Security Compass
Explore integrations
Security magnifying glass visualization