Automated Threat Modeling

Brief Summary: Oracle Access Manager CVE-2026-91522, an Unauthenticated SAML Flaw Leading to Takeover

A brief summary of CVE-2026-91522, an unauthenticated SAML flaw in the Authentication Engine of Oracle Access Manager 12.2.1.4.0 and 14.1.2.1.0 that can lead to product takeover. Includes patch information from Oracle's November 2026 Critical Security Patch Update.

CVE Analysis

7 min read

Gaurav Sarraf
Gaurav Sarraf

2026-11-17

Brief Summary: Oracle Access Manager CVE-2026-91522, an Unauthenticated SAML Flaw Leading to Takeover

Introduction

Oracle has patched a flaw in the Authentication Engine of Oracle Access Manager that lets an unauthenticated attacker with network access, communicating over SAML, take over the product. Oracle Access Manager is the component that handles authentication and access decisions for the applications behind it, so a takeover of OAM affects the identity layer itself. Oracle rates the issue CVSS 3.1 8.1.

Oracle Access Manager (OAM) is part of Oracle Fusion Middleware and forms the core of Oracle's Access Management offering. Oracle describes that offering as providing web single sign-on, multifactor authentication, authorization, session management, SAML federation and OAuth, with services hosted in Oracle WebLogic Server and enforced through access interceptors such as WebGates. Oracle Access Management was named a 2024 Gartner Peer Insights Customers' Choice for Access Management. That recognition is based on end-user reviews and is not a market share figure, but it does indicate the product is widely used as an enterprise authentication platform.

Technical Information

What Oracle Disclosed

Oracle's November 2026 Critical Security Patch Update (CSPU) text risk matrix describes the issue as follows:

  • Product: Oracle Access Manager, Oracle Fusion Middleware
  • Component: Authentication Engine
  • Protocol: SAML
  • Remotely exploitable without authentication: Yes
  • Published outcome: takeover of Oracle Access Manager
  • Affected supported versions: 12.2.1.4.0 and 14.1.2.1.0
  • CNA: Oracle

The description is limited to Oracle Access Manager. It does not establish that every Oracle Fusion Middleware component is affected by this CVE.

Reading the CVSS Vector

The published vector is CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H. It breaks down as follows:

  • AV:N: reachable over the network.
  • AC:H: high attack complexity. Conditions outside the attacker's control have to line up for exploitation to succeed.
  • PR:N: no privileges required. The attacker does not need a legitimate OAM account.
  • UI:N: no user interaction required.
  • S:U: scope unchanged.
  • C:H, I:H, A:H: high confidentiality, integrity and availability impact.

High complexity and no required privileges describe different properties, and they do not contradict each other. "Difficult to exploit" should not be read as "requires credentials."

The 8.1 figure is a CVSS Base Score. The FIRST CVSS v3.1 specification separates Base metrics, which describe a flaw's intrinsic characteristics, from Temporal metrics, which cover changing factors such as exploit code availability. The Base Score therefore says nothing about whether exploitation is occurring.

Root Cause: What Is and Is Not Known

OAM is closed source. Oracle has published no root cause analysis, code changes or commit diffs for this fix. Oracle's description states only that the patch changes how the OAM Authentication Engine handles SAML. The public record does not identify:

  • the specific SAML binding, endpoint, request parameter or malformed message involved
  • which conditions produce the high attack complexity rating
  • the vulnerable code path

VulDB classifies the issue as improper authentication, CWE-287, while also stating that technical details are unknown. The NVD entry lists no CWE, so CWE-287 should be treated as a third-party label rather than an official assignment. The takeover outcome alone does not tell us whether the technique is signature bypass, assertion replay, deserialization, command execution or something else. We are not going to speculate beyond what Oracle has stated.

Attack Flow at the Level of Public Detail

Based only on Oracle's description and the CVSS vector, the attack has this shape:

  1. The attacker has network reach to an OAM deployment that processes SAML traffic in the Authentication Engine.
  2. Without any credentials or victim interaction, the attacker sends SAML traffic to the Authentication Engine.
  3. If the conditions behind the AC:H rating are met, the Authentication Engine mishandles that traffic.
  4. The result is compromise of Oracle Access Manager, up to full takeover, with high confidentiality, integrity and availability impact.

The public sources give no detail for steps 2 and 3, so they cannot support an exploit-based validation procedure. Exposure assessment rests on two facts: the installed version, and whether the SAML path is reachable.

Exploitation Status

Rapid7 reports the CVE's CISA KEV status as false, and TheHackerWire reports it is not in KEV. TheHackerWire also reports no public proof of concept detected and no known ransomware campaign link. VulDB states that no exploit is publicly available. None of the reviewed sources name a threat actor or publish CVE-specific indicators. These statements describe public visibility only. They do not establish that no private exploit exists.

Patch Information

Oracle fixed CVE-2026-91522 in the November 2026 Critical Security Patch Update, released 2026-11-17. The advisory's Oracle Fusion Middleware risk matrix lists the issue as follows:

  • Product / component: Oracle Access Manager / Authentication Engine
  • Protocol: SAML
  • Remote without auth: Yes
  • CVSS 3.1: 8.1, CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
  • Patched release lines: 12.2.1.4.0 and 14.1.2.1.0
  • Patch availability document: Fusion Middleware, My Oracle Support Doc ID CPU450

Where the patch comes from. Oracle does not attach patch files to the advisory. The OAM row points to the Fusion Middleware Patch Availability Document (CPU450) on My Oracle Support. That document maps each supported OAM release to the correct patch and gives installation steps. Downloading the patch binaries requires an Oracle support login.

Support status. Oracle produces CSPU patches only for versions in Premier Support or Extended Support. A deployment on an older, unsupported OAM release will not receive a fix and must first upgrade to a supported line.

How this release differs from the usual schedule. CSPUs are a newer Oracle program that runs alongside the quarterly cumulative Critical Patch Updates (CPUs). This fix shipped on November 17, a month after the October 2026 CPU, and the October CPU does not include it. If you patched OAM for October, you still need to apply the November CSPU patch for this CVE.

Temporary measures. The advisory notes that blocking the network protocols an attack requires may reduce risk until patching is complete. Oracle also warns that such changes can break application functionality and should be tested on nonproduction systems first. Above all, they do not correct the underlying problem. Oracle's separate advice about removing unnecessary privileges does not apply here, because the vector is PR:N.

Affected Systems and Versions

  • Oracle Access Manager 12.2.1.4.0 (Oracle Fusion Middleware), Authentication Engine, reachable via SAML
  • Oracle Access Manager 14.1.2.1.0 (Oracle Fusion Middleware), Authentication Engine, reachable via SAML

These are the supported versions Oracle lists as affected. Older, unsupported releases are not listed, but that does not establish them as unaffected, and Oracle will not ship CSPU fixes for them.

There is one discrepancy in the source material. One upstream source listed the affected 14.x version as 14.1.2.0.0, but Oracle's advisory and text-form risk matrix both list 14.1.2.1.0. Use 14.1.2.1.0 when matching the CPU450 patch. When the patch information was compiled, NVD had not yet published the full vendor record, so Oracle's advisory is the authoritative source for the fix for now.

Vendor Security History

The most relevant precedent is CVE-2021-35587, a separate vulnerability in OAM's OpenSSO component. It allowed unauthenticated, HTTP-based compromise, including arbitrary code execution. The timeline went as follows:

  • January 2022: Oracle shipped a patch in that month's Critical Patch Update.
  • Months later: SecurityWeek reported that GreyNoise observed exploitation attempts beginning in September, increasing in October and November.
  • November 30, 2022: Belgium's Centre for Cybersecurity (CCB) published an advisory warning of active exploitation.
  • Afterward: CISA added the flaw to its Known Exploited Vulnerabilities catalog and directed federal agencies to remediate it.

That case shows attackers targeting OAM well after a fix was available. It does not carry over to CVE-2026-91522 in terms of root cause, technique or actors, because the components (OpenSSO vs. Authentication Engine) and protocols (HTTP vs. SAML) differ.

For broader context, Oracle's November 2026 advisory reports 71 new Fusion Middleware security patches, 53 of which address vulnerabilities potentially exploitable remotely without authentication. These are suite-wide counts, not OAM-specific figures.

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