Automated Threat Modeling

Brief Summary: CVE-2026-91500, a CVSS 10.0 Unauthenticated Flaw in the Oracle Access Manager Authentication Engine

A brief summary of CVE-2026-91500, a CVSS 3.1 10.0 vulnerability in the Authentication Engine of Oracle Access Manager 12.2.1.4.0 and 14.1.2.1.0 that unauthenticated attackers can reach over HTTP. Covers what Oracle has disclosed, the scope of the impact, and how the November 2026 Critical Security Patch Update delivers the fix.

CVE Analysis

8 min read

Gaurav Sarraf
Gaurav Sarraf

2026-11-17

Brief Summary: CVE-2026-91500, a CVSS 10.0 Unauthenticated Flaw in the Oracle Access Manager Authentication Engine

Introduction

According to Oracle's November 2026 advisory, an unauthenticated attacker who can reach Oracle Access Manager over HTTP may be able to read, create, modify, or delete critical data managed by the product. Access Manager sits in front of other enterprise applications as a centralized authentication and authorization layer. Oracle also warns that attacks on CVE-2026-91500 may significantly impact additional products, and it has assigned the flaw the maximum CVSS 3.1 base score of 10.0.

Oracle Access Manager (OAM) is a Java EE enterprise security application within Oracle Fusion Middleware that centralizes authentication and authorization and restricts access to confidential information. Oracle positions it as the Fusion Middleware single sign-on solution, and it integrates with other Oracle products. For example, it provides single sign-on support for Oracle Forms applications. Reporting on Gartner's 2021 Magic Quadrant for Access Management placed Oracle in the Niche Players quadrant. The Gartner Peer Insights product page currently shows a 4.9 rating from 220 ratings, which points to an established enterprise footprint rather than a niche deployment base.

Technical information

What Oracle has disclosed

The vulnerability is in the Authentication Engine component of Oracle Access Manager. Oracle's Fusion Middleware risk matrix lists the protocol as HTTP and marks Remote Exploit without Auth. as Yes. Oracle describes the issue as easily exploitable by an unauthenticated attacker with network access via HTTP.

Oracle states that a successful attack can result in:

  • unauthorized access to critical data, or complete access to all Oracle Access Manager accessible data
  • unauthorized creation, deletion or modification of critical data, or of all Oracle Access Manager accessible data
  • a partial denial of service of Oracle Access Manager
  • significant impact on additional products beyond Oracle Access Manager (scope change)

Oracle does not identify which additional products may be affected. Given OAM's role as a single sign-on and authorization layer, the scope change is plausible in context, but the advisory itself does not name connected applications. The Oracle Forms integration shows how OAM is deployed. It does not mean every Forms deployment is affected.

Root cause: not publicly disclosed

We could not find a public explanation of the underlying bug, and that is expected for this product:

  • Oracle Access Manager is closed source, so there is no public commit, diff or changelog.
  • Oracle has not said what it changed inside the Authentication Engine.
  • The NVD entry does not assign a CWE.
  • VulDB labels the issue CWE-404, but marks that classification as unconfirmed. We do not treat it as an established root cause.

The public description does not establish whether the flaw is an authentication bypass, an injection, a deserialization issue, or something else. It also does not establish arbitrary code execution. The confirmed facts are the exposure conditions (unauthenticated, network, HTTP) and the consequences (data access and modification, partial denial of service, scope change). The internal exploit chain remains undisclosed.

CVSS vector breakdown

Oracle publishes the following vector:

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:L
  • AV:N (Attack Vector: Network): reachable remotely
  • AC:L (Attack Complexity: Low): no special conditions are required
  • PR:N (Privileges Required: None): no account is needed
  • UI:N (User Interaction: None): no victim action is required
  • S:C (Scope: Changed): impact can extend beyond OAM itself
  • C:H / I:H (Confidentiality and Integrity: High): extensive data disclosure and modification
  • A:L (Availability: Low): partial denial of service

The score reaches 10.0 because of the changed scope combined with high confidentiality and integrity impact. The availability component is Low, so the maximum score should not be read as a confirmed complete outage. Under the FIRST CVSS v3.1 specification, the Base Score captures intrinsic characteristics and reasonable worst-case impact. Exploit availability belongs in Temporal metrics, so a 10.0 is not evidence that an exploit or campaign exists.

Attack flow

Based only on what Oracle has published, the documented attack path looks like this:

  1. The attacker has network access to the HTTP interface of an Oracle Access Manager deployment running 12.2.1.4.0 or 14.1.2.1.0 without the November 2026 security patches.
  2. The attacker needs no credentials and no interaction from any user.
  3. The attacker interacts with the Authentication Engine over HTTP. Oracle has not disclosed the vulnerable endpoint, request format, payload, or affected function.
  4. On success, the attacker can read or tamper with critical data accessible to OAM, cause a partial denial of service, and potentially affect additional products that depend on OAM.

We deliberately stop at that level of detail. Nothing in the public record supports a more specific reconstruction.

Exploitation status

The reviewed sources do not confirm active exploitation of CVE-2026-91500. The Rapid7 and VulDB records identify no campaign, no public exploit, and no named threat actor. We found no verified public proof of concept and no CVE-specific indicators of compromise.

CISA KEV status could not be definitively established. The retrieved catalog page is a paginated view (1 to 20 of 1,782 results), and the retrieved feed excerpt (catalog version 2026.11.17) was incomplete. VulDB shows a KEV value of "no", but that is a third-party field. These gaps limit what we can say. They do not show that exploitation or private exploit development is absent.

Patch information

Where the fix lives. Oracle fixed CVE-2026-91500 in its November 2026 Critical Security Patch Update (CSPU), released on November 17, 2026 (advisory Rev 1, initial release). The CVE appears in the Oracle Fusion Middleware risk matrix with these values: product Oracle Access Manager, component Authentication Engine, protocol HTTP, Remote Exploit without Auth. Yes, and CVSS 3.1 10.0. Both the NVD and CVE.org records point back to this advisory as the only vendor reference.

Which builds need it. The affected supported versions are 12.2.1.4.0 and 14.1.2.1.0. Oracle publishes affected baselines, not a fixed version string. A patched system will not show a new OAM version number. It will show the same 12.2.1.4.0 or 14.1.2.1.0 baseline with the November 2026 security patches applied on top. To confirm an install is fixed, check the installed patch inventory (for example with OPatch). Comparing version numbers will not tell you.

How to get the patch. The patches and installation steps are in the Fusion Middleware Patch Availability Document, My Oracle Support Document ID CPU450, which is linked from the advisory. Downloading them requires a valid Oracle Support contract. The advisory also references KA1182 for the full list of current and previously released Fusion Middleware patches. CSPU patches are built only for versions in Premier or Extended Support. If you run an OAM release outside those versions, no fix exists for it, and you would need to upgrade to a supported baseline first.

How this release differs from the quarterly cycle. CSPUs are a new monthly release type. Oracle describes them as a smaller, more focused format for targeted, high-priority fixes. They sit alongside the quarterly cumulative Critical Patch Updates (CPUs) rather than replacing them. The November CSPU is therefore a separate patch drop, and the next cumulative CPU is due in January 2027. Teams that patch OAM only on the quarterly cycle would not receive this fix until then.

Bundled OAM fixes. The same advisory fixes a large group of other Oracle Access Manager CVEs, including CVE-2026-91498, CVE-2026-91507, CVE-2026-91509, CVE-2026-91510, CVE-2026-91516, CVE-2026-91522, CVE-2026-91531, CVE-2026-91533, CVE-2026-91540, CVE-2026-91543, CVE-2026-91564, CVE-2026-91671 and CVE-2026-114835. Several of these are in the same Authentication Engine component and are reachable over HTTP, SAML, TCP or LDAP. Oracle delivers them together through the CPU450 patch set, so installing the November 2026 Fusion Middleware patches for OAM fixes CVE-2026-91500 along with the rest of the group. Oracle does not offer a separate fix for this CVE alone. Given the rating, Oracle advises applying CSPU patches "as soon as possible."

Interim risk reduction. Oracle's advisory notes that blocking the network protocols required for an attack may temporarily reduce risk until patches are applied. Oracle also cautions that this may break application functionality and does not correct the underlying problem, and it recommends testing such changes on nonproduction systems first. Neither the advisory nor the CVE records provide a CVE-specific blocking rule, endpoint, or configuration example. Oracle's general advice about removing unnecessary privileges does not apply here, because this vulnerability requires no authentication.

Affected systems and versions

  • Product: Oracle Access Manager (Oracle Fusion Middleware)
  • Component: Authentication Engine
  • Affected supported versions: 12.2.1.4.0 and 14.1.2.1.0
  • Attack channel: HTTP, unauthenticated, network accessible
  • Vulnerable configuration: deployments on either of those baselines without the November 2026 CSPU patches from CPU450 applied

The version list covers only the supported releases Oracle explicitly names. It is not a safety statement about older releases. Oracle states that releases outside Premier Support or Extended Support are not tested for the vulnerabilities addressed in this update, and it recommends upgrading to supported versions.

Vendor security history

Oracle Access Manager has a documented history of severe, unauthenticated, HTTP-reachable vulnerabilities. Belgium's Centre for Cybersecurity documented CVE-2021-35587, a flaw in the OpenSSO component with a CVSS score of 9.8. The CCB advisory stated it was actively exploited and described unauthenticated remote access via HTTP, with potential full compromise and arbitrary code execution. Oracle addressed it with a patch, and CCB recommended patching with the highest priority after thorough testing.

The two issues should be kept separate:

  • Component: CVE-2021-35587 affected OpenSSO. CVE-2026-91500 affects the Authentication Engine. A shared root cause should not be assumed.
  • Impact: CCB described code execution for the older flaw. For CVE-2026-91500, Oracle describes data access and modification, partial denial of service, and scope change, with no mention of code execution.
  • Exploitation: the older flaw had documented active exploitation. For the newer one, exploitation is not confirmed in the reviewed sources.

The newer vulnerability has the higher published score, while the older one has stronger evidence of real-world exploitation. Oracle's own November 2026 advisory adds that attackers have sometimes succeeded because customers did not apply available Oracle patches. That is a general vendor statement and does not report an incident involving this CVE. Together with the number of other Access Manager CVEs fixed in the same release, it is a reason to treat OAM patch cadence as a standing operational concern.

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