Automated Threat Modeling

Quick Look: Oracle Access Manager CVE-2026-91509, an Unauthenticated SAML Flaw in the Authentication Engine

A brief summary of CVE-2026-91509, a High-severity (CVSS 8.7) flaw in the Oracle Access Manager Authentication Engine that an unauthenticated attacker can reach over SAML. It covers the published impact, affected versions and the November 2026 Critical Security Patch Update.

CVE Analysis

8 min read

Gaurav Sarraf
Gaurav Sarraf

2026-11-17

Quick Look: Oracle Access Manager CVE-2026-91509, an Unauthenticated SAML Flaw in the Authentication Engine

Introduction

Oracle's November 2026 Critical Security Patch Update fixes a flaw in the Oracle Access Manager Authentication Engine that an unauthenticated attacker can reach over SAML. Oracle's published outcome is high confidentiality and integrity impact on the data the product can access. Oracle Access Manager typically sits in front of other enterprise applications as the single sign-on and federation layer, so Oracle's scope change rating signals that a successful attack may significantly affect products beyond Access Manager itself.

Oracle Access Manager is part of Oracle Fusion Middleware and underpins Oracle Access Management. Oracle Access Management provides multifactor authentication and single sign-on across cloud and on-premises environments, and can be deployed in Oracle Cloud Infrastructure or customer data centers. Oracle reports that it was recognized as a 2024 Gartner Peer Insights Customers' Choice for Access Management based on reviews from end-user professionals, although no public market share figure exists for the affected releases. Its SAML federation component can act as an identity provider, a service provider, or both, which places it on the trust boundary between organizations and the applications that rely on it.

Technical information

What Oracle has disclosed

Oracle rates CVE-2026-91509 as High with a CVSS 3.1 base score of 8.7:

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

Based on Oracle's description, each metric means the following for this vulnerability:

  • Attack vector, Network (AV:N): the vulnerable functionality is reachable over a network via SAML.
  • Attack complexity, High (AC:H): Oracle describes exploitation as difficult. The specific additional conditions are not disclosed. AC:H does not imply that authentication is required.
  • Privileges required, None (PR:N): the attacker needs no existing account or session.
  • User interaction, None (UI:N): no other user has to participate.
  • Scope, Changed (S:C): Oracle warns that attacks may significantly impact additional products. FIRST's CVSS specification defines changed scope as effects beyond the vulnerable component's security authority. Oracle does not name the additional products, and the disclosure does not establish that every federated application is affected.
  • Confidentiality, High (C:H): unauthorized access to critical data or complete access to all data accessible to Oracle Access Manager.
  • Integrity, High (I:H): unauthorized creation, deletion or modification of critical data or all data accessible to Oracle Access Manager.
  • Availability, None (A:N): no availability impact is assigned. That rating does not mean every operational consequence has been tested.

Root cause: what is and is not known

Oracle Access Manager is closed source, and Oracle has published no root cause, no CWE classification and no description of the code change. The CVE record carries no CWE identifier. VulDB separately labels the issue CWE-285, Improper Authorization, but that label comes from a third-party database, not from Oracle's CNA record.

The public disclosure does not identify a vulnerable URL, an affected SAML binding, a malicious assertion format, a signature validation failure or a reproducible exploitation procedure. Based on the published facts, it would be unsupported to call this a confirmed SAML signature bypass, an XML parsing attack or a remote code execution bug.

What we can reasonably infer is narrow. The attack enters through SAML and lands in the Authentication Engine, so the fix most likely changes how the Authentication Engine processes or validates SAML input. Oracle has not confirmed which check was added or tightened, so treat this as an inference. Independent technical detail will probably only emerge if researchers diff patched and unpatched builds.

SAML federation context

Oracle's federation documentation shows where SAML traffic enters the product. Identity Federation can act as identity provider, service provider, or both, with trusted partner profiles defining the remote parties. Documented flows include:

  1. A service provider sends an authentication request to an identity provider.
  2. An identity provider sends an unsolicited assertion response.
  3. A SAML exchange in which the request travels over HTTP Redirect and the response over HTTP POST.

These flows describe the normal attack surface. None of them has been identified as the vulnerable binding, endpoint or message sequence for this CVE.

Attack flow, as far as the public record supports it

Oracle has published no exploit mechanics, so the most we can describe is the attack model implied by the advisory:

  1. The attacker locates an Oracle Access Manager deployment (12.2.1.4.0 or 14.1.2.1.0) whose SAML functionality is reachable over the network.
  2. The attacker interacts with that functionality without credentials and without involving any legitimate user.
  3. The attacker must satisfy additional, undisclosed conditions, which is why Oracle rates the attack as difficult.
  4. If successful, the attacker can read, create, modify or delete critical data or all data accessible to Oracle Access Manager.
  5. Because scope is changed, the compromise may extend to other products, such as applications that depend on Oracle Access Manager for single sign-on. Oracle does not specify which products.

Exploitation status

  • CISA KEV: Rapid7 reports KEV status as false, and TheHackerWire also reports the CVE as not recorded. The CISA catalog page we reviewed is paginated, so this status comes from those trackers rather than from a full direct check of the catalog.
  • Public exploit code: TheHackerWire reports no confirmed public exploit and no public proof of concept.
  • Threat actors and campaigns: none named or documented.
  • Indicators of compromise: no CVE-specific infrastructure, payloads or incident artifacts have been published.

Exploitation is therefore unconfirmed, but it has not been disproved. The CVSS base score measures intrinsic severity and reasonable worst-case impact, not observed attack activity. At the time of review, the NVD page displayed "CVE ID Not Found", while the CVE.org record and Rapid7 both give a publication date of 17 November 2026.

Patch information

Oracle fixed CVE-2026-91509 in the November 2026 Critical Security Patch Update (CSPU), released on 17 November 2026 (advisory Rev 1, initial release). Oracle Access Manager is closed source, so there is no public commit or diff. Everything here comes from Oracle's advisory material.

Advisory entry. The Oracle Fusion Middleware risk matrix in the November 2026 CSPU lists CVE-2026-91509 with the following details:

  • Product: Oracle Access Manager (Oracle Fusion Middleware)
  • Component: Authentication Engine
  • Protocol: SAML
  • Remotely exploitable without authentication: Yes
  • CVSS 3.1: 8.7, CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:N
  • Supported versions affected: 12.2.1.4.0, 14.1.2.1.0
  • Notes: None

Oracle's risk matrices list the vulnerabilities that a release's patches newly fix. Its listing here therefore means the November 2026 Fusion Middleware patches for both release lines contain the fix. Oracle gives no fixed version string. The listed versions are the affected baselines, and the fix is installed on top of them.

Getting the patch. The advisory does not link to a public download. Its Patch Availability Document column for Fusion Middleware points to My Oracle Support Note CPU450, which also cites KA1182. That note explains which patches exist for each Fusion Middleware product and release, and how to install them. Oracle's announcement blog also refers to an executive summary on My Oracle Support (Doc ID CPU433). Access requires a valid Oracle support contract, so in practice the patch is available only to licensed customers.

Why the CSPU format matters. The fix shipped in a Critical Security Patch Update rather than a quarterly Critical Patch Update (CPU). Oracle describes CSPUs as a smaller, more focused format for targeted, high-priority security fixes, and says they supplement the quarterly cumulative CPUs rather than replace them. In practice:

  • Do not wait for the next quarterly CPU. The fix is available now, and Oracle released it outside the quarterly cycle because it rated it high priority.
  • Apply the whole Oracle Access Manager patch, not just this one fix. The same matrix lists 13 other Oracle Access Manager CVEs: CVE-2026-114835, CVE-2026-91498, CVE-2026-91500, CVE-2026-91507, CVE-2026-91510, CVE-2026-91516, CVE-2026-91522, CVE-2026-91531, CVE-2026-91533, CVE-2026-91540, CVE-2026-91543, CVE-2026-91564 and CVE-2026-91671. Several are in the same Authentication Engine component. Applying the full November 2026 Oracle Access Manager patch for your release line fixes all of them together.

Interim measures. Oracle's advisory guidance says that blocking network protocols required by an attack may reduce risk until patches are applied. This is general advice, not a CVE-specific SAML filtering rule. Restricting SAML can break legitimate federation, so Oracle recommends testing such changes on nonproduction systems first. Oracle states explicitly that these workarounds do not correct the underlying problem and are not a long-term solution. Oracle's advice about removing unnecessary privileges does not apply here, because this flaw requires no privileges.

Affected systems and versions

Oracle lists these supported versions of Oracle Access Manager (Oracle Fusion Middleware) as affected:

  • 12.2.1.4.0
  • 14.1.2.1.0

The vulnerable component is the Authentication Engine, and the attack path is SAML over the network. Oracle does not publish a minimum fixed version. Remediation means applying the November 2026 CSPU patch on top of these baselines.

Oracle evaluates only supported releases. Unsupported releases are not tested for these vulnerabilities, so their absence from the affected list is not evidence that they are safe. Oracle recommends upgrading to a supported version.

Vendor security history

Oracle Access Manager has a precedent for real-world exploitation. On 30 November 2022, Belgium's Centre for Cybersecurity warned that CVE-2021-35587, a different Oracle Access Manager vulnerability in the OpenSSO component, was being actively exploited. That flaw allowed unauthenticated access via HTTP and could enable privileged user creation, lateral movement or arbitrary code execution.

That history shows Oracle Access Manager is a target in practice. It does not show that CVE-2026-91509 shares a root cause, protocol, consequence or exploitation status with the earlier bug. The present issue is in the Authentication Engine and is reached via SAML, and no exploitation has been confirmed.

Oracle's published remediation practices identify Critical Patch Updates as its main channel for backporting security fixes to on-premises products. They also allow for Security Alerts or workarounds for particularly critical vulnerabilities or reported active exploitation. Oracle has acknowledged cases in which attackers succeeded because customers had not applied available patches. The November 2026 CSPU, released outside the quarterly cycle, fits that pattern of shipping high-priority fixes separately.

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