Automated Threat Modeling

Brief Summary: Oracle Access Manager CVE-2026-91531, an Unauthenticated HTTP Flaw in the Authentication Engine

A brief summary of CVE-2026-91531, an unauthenticated HTTP vulnerability in the Authentication Engine of Oracle Access Manager 12.2.1.4.0 and 14.1.2.1.0 with a changed-scope CVSS 3.1 score of 7.2. The post covers the published impact, Oracle's November 2026 CSPU patch details, and the current exploitation picture.

CVE Analysis

7 min read

Gaurav Sarraf
Gaurav Sarraf

2026-11-17

Brief Summary: Oracle Access Manager CVE-2026-91531, an Unauthenticated HTTP Flaw in the Authentication Engine

Introduction

Oracle Access Manager often sits in front of an organization's internal and customer-facing applications as the single sign-on and policy enforcement point, so a flaw in its Authentication Engine matters well beyond the product itself. CVE-2026-91531, fixed in Oracle's November 2026 Critical Security Patch Update, can be reached by an unauthenticated attacker over HTTP. Oracle scores it with a changed scope because attacks may significantly impact additional products.

Oracle Access Manager (OAM) is the Oracle Fusion Middleware single sign-on solution. It is part of the broader Oracle Access Management application, which Oracle describes as an enterprise security application providing web perimeter security and web single sign-on. Its feature set includes multifactor authentication, authorization, session management, SAML federation and OAuth, plus integration with Oracle Identity Cloud Service for hybrid access across on-premises and cloud applications. Oracle reports receiving 2024 Gartner Peer Insights Customers' Choice recognition for Access Management, which places OAM squarely in the enterprise identity market, although the sources we reviewed do not provide market share figures.

Technical information

What Oracle discloses

Oracle identifies the vulnerable component as the Authentication Engine within Oracle Access Manager. According to the CVE record, this is an easily exploitable vulnerability that allows an unauthenticated attacker with network access via HTTP to compromise Oracle Access Manager. Successful attacks can result in:

  • Unauthorized update, insert or delete access to some Oracle Access Manager accessible data
  • Unauthorized read access to a subset of Oracle Access Manager accessible data
  • Possible significant impact on additional products (scope change)

The published vector is:

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

Reading the CVSS vector

  • Attack Vector: Network. Remotely reachable, and the description specifies HTTP.
  • Attack Complexity: Low. Oracle scores exploitation as easy.
  • Privileges Required: None. No existing account is needed.
  • User Interaction: None. No victim action is required.
  • Scope: Changed. The impact can cross into components outside OAM's own security authority.
  • Confidentiality: Low. Read access to a subset of accessible data.
  • Integrity: Low. Modification of some accessible data.
  • Availability: None. The vector assigns no availability impact.

The scope change is the detail we would focus on. OAM brokers authentication and policy decisions for the applications behind it, so a flaw in its Authentication Engine can affect data in other products as well as in OAM. Oracle does not enumerate which additional products may be affected, and the record does not establish that every integrated application is impacted.

Root cause: what is not public

Oracle does not publish source diffs, commit references or root cause details for CSPU fixes. The advisory and CVE record do not identify an endpoint, port, HTTP method, request parameter or payload. NVD's weakness field is empty, so there is no authoritative CWE mapping. VulDB describes the issue as "improper authorization", but that is a secondary classification rather than a disclosed implementation-level root cause.

Although the vulnerable component handles authentication, the public description does not establish credential theft, session forgery, arbitrary code execution, operating system compromise or full administrative takeover. The confirmed impact is limited confidentiality and integrity exposure with a changed scope. No vulnerable code snippets are available.

Attack flow based on the published metrics

Without an implementation-level description, the attack flow can only be stated at the level Oracle provides:

  1. The attacker needs network reachability to the HTTP interface of an affected OAM deployment (12.2.1.4.0 or 14.1.2.1.0).
  2. No credentials, prior session or victim interaction are required.
  3. The attacker interacts with the Authentication Engine over HTTP in a way Oracle has not disclosed. Oracle rates the complexity as low.
  4. On success, the attacker can read a subset of OAM accessible data and update, insert or delete some of it.
  5. Because the scope is changed, effects can extend to additional products that rely on OAM, which Oracle does not name.

Exploitation status

We found no confirmed exploitation in the reviewed sources. Rapid7 lists CISA KEV membership as "False" and shows EPSS score and percentile as "N/A", which means unavailable rather than zero. VulDB states that no exploit is available, and no threat actor attribution or campaign was identified. A third-party page references a scanner command containing this CVE identifier, but it labels its detection templates as generic, which does not establish a working CVE-specific template or proof of concept. Easy exploitability and observed exploitation are separate questions, and the current evidence supports only the first.

Patch information

Oracle fixed CVE-2026-91531 in its November 2026 Critical Security Patch Update (CSPU), released on 2026-11-17 (advisory Rev 1, initial release). The fix covers the Authentication Engine component of Oracle Access Manager on both supported release lines named in the advisory, 12.2.1.4.0 and 14.1.2.1.0. NVD's entry points to this advisory as its only reference.

Oracle's risk matrix lists CVE-2026-91531 under Oracle Access Manager / Authentication Engine with:

  • Protocol: HTTP
  • Remotely exploitable without authentication: Yes
  • CVSS 3.1 base score: 7.2

The advisory text does not name a CWE, a patch number or a fixed build string, so the fix can only be described at the advisory level.

Obtaining and applying the fix:

  • Patch Availability Document: The advisory's Fusion Middleware row links to My Oracle Support document CPU450, which lists the patch numbers and installation steps for each OAM release line. Patches are downloaded through My Oracle Support and require a valid support contract.
  • Full Fusion Middleware patch list: Oracle points to My Oracle Support Doc ID KA1182 for every current and earlier CSPU and Critical Patch Update (CPU) patch for Fusion Middleware. Oracle states that CSPUs complement the cumulative quarterly CPUs rather than replace them, so administrators should confirm that each OAM home already has the earlier required CPU and CSPU patches and review earlier advisories for previously released fixes.
  • Scope of the release: This CSPU contains 71 new Fusion Middleware security patches, of which Oracle says 53 may be exploitable over the network without credentials. CVE-2026-91531 is one of several OAM Authentication Engine CVEs fixed in the same cycle, so applying the OAM patch set addresses them together.

Interim measures: Oracle notes that blocking the network protocols required for an attack may reduce risk until patches are applied. For this CVE that protocol is HTTP, so blocking it may disrupt OAM functionality. Oracle recommends testing such changes on nonproduction systems and is explicit that this does not fix the underlying vulnerability. Oracle's general advice about removing unnecessary privileges does not help here, because the attack requires no privileges.

Oracle's guidance is to apply security patches without delay and to remain on actively supported versions.

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
  • Exposure condition: The affected service is reachable by an attacker over HTTP, and no authentication is required

Oracle notes that releases outside Premier Support or Extended Support are not tested for the vulnerabilities covered by the update, and that earlier versions of affected releases are likely also affected. The two listed versions should not be read as evidence that older or unsupported releases are safe.

Vendor security history

Oracle Access Manager has a documented prior case of in-the-wild exploitation. Oracle patched CVE-2021-35587, a flaw in the OpenSSO component, in January 2022. Belgium's Centre for Cybersecurity published an advisory on November 30, 2022 reporting that it was actively being exploited. That advisory described remote unauthenticated access via HTTP, with outcomes including creation of users with arbitrary privileges or arbitrary code execution, and recommended patching and reviewing system and network logs for suspicious activity.

The comparison is useful but limited. CVE-2021-35587 affected a different component and had a far broader disclosed impact than CVE-2026-91531, which has no reported exploitation and no disclosed code execution path. The earlier case does show that serious OAM vulnerabilities have attracted real attacks well after a patch was published, so patch availability and actual protection should not be treated as the same thing.

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