Automated Threat Modeling

Brief Summary: Oracle Access Manager CVE-2026-91510, an Unauthenticated Authentication Engine Flaw Rated CVSS 10.0

A brief summary of CVE-2026-91510, a CVSS 10.0 unauthenticated HTTP vulnerability in the Oracle Access Manager Authentication Engine affecting releases 12.2.1.4.0 and 14.1.2.1.0, with patch information from Oracle's November 2026 Critical Security Patch Update.

CVE Analysis

8 min read

Gaurav Sarraf
Gaurav Sarraf

2026-11-17

Brief Summary: Oracle Access Manager CVE-2026-91510, an Unauthenticated Authentication Engine Flaw Rated CVSS 10.0

Introduction

Oracle Access Manager often sits in front of enterprise applications as the component that decides who gets in. A flaw in its Authentication Engine that needs no credentials and no user interaction therefore matters well beyond the product itself. Oracle rated CVE-2026-91510 at CVSS 10.0 and fixed it in the November 2026 Critical Security Patch Update, about a month after the October quarterly release. That timing means environments fully patched through October are still exposed.

Oracle Access Manager (OAM) is part of Oracle Fusion Middleware and provides centralized authentication, authorization, and single sign-on. Applications delegate access decisions to it, and registered agents enforce its policies in front of protected applications. Oracle positions the product across cloud and on-premises environments. Gartner Peer Insights lists it, and Oracle reports a 2025 Customers' Choice designation, although no verified market share figure is available. Because OAM is a centralized access-control layer, the changed scope in Oracle's rating for this CVE carries extra weight.

Technical Information

What the public record establishes

  • Product: Oracle Access Manager, Oracle Fusion Middleware
  • Component: Authentication Engine
  • Protocol: HTTP
  • Authentication required: None
  • Affected supported releases: 12.2.1.4.0 and 14.1.2.1.0
  • CVSS 3.1 base score: 10.0
  • Published: November 17, 2026, with Oracle as the CNA

The published vector is:

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

Here is what each metric means for this issue:

  • AV:N, AC:L: The attack works remotely over the network, and Oracle calls it easily exploitable.
  • PR:N, UI:N: The attacker needs no account, and no victim has to take any action.
  • S:C: The impact can cross a security boundary. Oracle states that attacks may significantly impact additional products, but does not name them.
  • C:H, I:H: The attacker can gain unauthorized access to critical data or all OAM-accessible data. They can also create, delete, or modify that data.
  • A:L: Partial denial of service of OAM is possible. The record does not describe a complete outage.

The CNA record and Rapid7 agree on this vector and score. Oracle's text-form risk matrix contains some inconsistent scoring text. We do not read that as evidence of a different attack model.

Root cause: what is not known

Oracle has not disclosed what changed inside the Authentication Engine. No source code, commit, or diff is public. The reviewed records contain no endpoint, request format, vulnerable parameter, or payload, and VulDB states that the technical details are unknown. We therefore cannot say whether the defect is an injection, a deserialization issue, a logic flaw in authentication handling, or something else.

The Oracle CNA record has no CWE assignment. VulDB separately labels the issue CWE-269, a privileges management weakness. That is a third-party classification, not a root cause Oracle has confirmed.

Attack flow based on the public record

The following sequence uses only the documented attack conditions and impacts.

  1. The attacker finds an OAM deployment on 12.2.1.4.0 or 14.1.2.1.0 that does not have the November 2026 CSPU applied, and has HTTP network reach to the Authentication Engine.
  2. Without credentials, the attacker sends HTTP traffic to the Authentication Engine. No user interaction is needed. The specific requests involved are not public.
  3. If the attack succeeds, the attacker gains unauthorized access to critical data or all OAM-accessible data.
  4. The attacker can create, modify, or delete that data.
  5. The attack can partially degrade OAM availability.
  6. Because the scope is changed, effects may extend to additional products. Oracle does not identify which products or describe how the impact spreads.

OAM's deployment model helps explain the scope rating, since applications rely on OAM for authentication and authorization decisions. However, the record does not establish that every protected application or connected identity store is compromised when OAM is. The record also does not describe remote code execution.

Exploitation status

Active exploitation is not publicly confirmed in the sources we reviewed, and no threat actor, campaign, or indicator set has been attributed. Several sources fill in the picture:

  • Rapid7 lists the CVE as not included in the CISA KEV catalog, and lists its EPSS score and percentile as N/A.
  • The official CISA material we reviewed was not complete enough to confirm independently that the CVE is absent from every CISA record.
  • VulDB reports no available exploit.
  • Oracle's disclosure policy limits technical detail, and Oracle does not distribute proof-of-concept code.

The lack of a public exploit is a statement about available evidence. It does not mean the vulnerability is hard to exploit.

Patch Information

Oracle fixed CVE-2026-91510 in its November 2026 Critical Security Patch Update (CSPU), released on November 17, 2026 (advisory Rev 1, initial release). Oracle has not published a fixed version number, a patch number, or a code diff. The fix is a closed-source binary patch for Oracle Fusion Middleware, distributed through My Oracle Support.

CSPU versus quarterly CPU

Oracle describes a CSPU as a smaller package of targeted, high-priority fixes. A CSPU adds to the quarterly cumulative Critical Patch Updates (CPUs) and does not replace them. Two planning points follow from this:

  • The October 2026 CPU does not cover this CVE, so an OAM instance that is fully patched through October is still exposed. Only the November CSPU fixes CVE-2026-91510.
  • Oracle tells customers to review previous CPU and CSPU advisories for earlier security patches. Confirm your OAM baseline is current before you apply the November fix on top of it.

Obtaining and applying the fix

  1. In the advisory, open the Patch Availability Document for Fusion Middleware (My Oracle Support document CPU450). It maps each product and version to the correct patch and includes installation instructions.
  2. Oracle's release blog also points to the CSPU executive summary on My Oracle Support (Doc ID CPU433).
  3. Download the OAM patch for your release line (12.2.1.4.0 or 14.1.2.1.0). Apply it with your standard OPatch process for Fusion Middleware. The binaries require an active Oracle support contract.

The CSPU contains 71 new Fusion Middleware security patches. Oracle says 53 of those vulnerabilities may be remotely exploitable without authentication. Several other OAM Authentication Engine flaws affecting the same two releases are fixed in the same update:

  • CVE-2026-91500: HTTP, CVSS 10.0, with the same vector as CVE-2026-91510.
  • CVE-2026-91507, CVE-2026-91533, CVE-2026-91531: other HTTP-based issues.
  • CVE-2026-91498, CVE-2026-91509, CVE-2026-91522: SAML-based issues.
  • CVE-2026-91516, CVE-2026-91543: TCP-based issues.
  • CVE-2026-91564: an LDAP-based issue.

The update also fixes CVE-2026-114835, a CVSS 10.0 flaw in the OAM Admin Console. These authentication path bugs ship together, so the practical approach is to apply the full CSPU. Patching for CVE-2026-91510 alone is not a realistic option.

Before the patch is applied

Oracle's general CSPU guidance is that blocking the network protocol an attack requires may temporarily reduce risk. For this CVE, that protocol is HTTP access to the OAM Authentication Engine. Oracle also warns that such restrictions:

  • can break functionality
  • should be tested outside production first
  • are not a long-term fix, because they do not correct the underlying flaw

Oracle does not publish a CVE-specific endpoint block, WAF signature, or configuration workaround. Oracle's advisory also suggests removing unnecessary privileges, but that advice applies to attacks that require privileges. It does not help against this unauthenticated (PR:N) issue.

A note on NVD status

Our sources disagree on NVD's status for this CVE. One check returned "CVE ID Not Found" from NVD, even though Oracle, acting as the CNA, has published the record. Use Oracle's advisory as the source of truth for fix status.

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

Treat any OAM deployment on either release line without the November 2026 CSPU as vulnerable. This includes instances patched through the October 2026 CPU.

Oracle does not test releases outside Premier or Extended Support against the issues in this CSPU, but says those releases are probably affected. Its guidance is to upgrade to a supported release and then apply the patch. The CVE record does not establish that any release other than the two listed is safe.

Vendor Security History

Oracle Access Manager has a documented history of serious exploitation. CVE-2021-35587 affected OAM's OpenSSO component and was patched by Oracle in January 2022. Belgium's Centre for Cybersecurity (CCB) later warned that it was being actively exploited. According to the CCB, the flaw allowed unauthenticated HTTP access, creation of privileged users, lateral movement, and arbitrary code execution. The CCB recommended prompt patching and a review of system and network logs.

That case involved a different component and a different documented impact. Its code execution capability and exploitation status should not be carried over to CVE-2026-91510. It does show how an unauthenticated flaw in this product class has been used in practice.

On process, Oracle delivers security fixes through quarterly CPUs, with CSPUs for targeted fixes. Security updates are available to active support customers through My Oracle Support. Oracle's disclosure policy limits vulnerability specifics and excludes exploit code, which is why public technical detail for this CVE is sparse. Oracle also warns that attackers have previously exploited vulnerabilities in systems where available patches had not been applied.

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