Automated Threat Modeling

Brief Summary: Oracle Access Manager CVE-2026-91507, Unauthenticated HTTP Flaw in the Authentication Engine (CVSS 9.3)

A brief summary of CVE-2026-91507, a CVSS 9.3 flaw in the Oracle Access Manager Authentication Engine that an unauthenticated attacker can reach over HTTP. Covers affected versions and 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-91507, Unauthenticated HTTP Flaw in the Authentication Engine (CVSS 9.3)

Introduction

Oracle Access Manager sits in front of enterprise applications and decides who gets a session, so a flaw in its Authentication Engine matters to every application that trusts it for sign-in. CVE-2026-91507, fixed in Oracle's November 2026 Critical Security Patch Update, can be reached by an unauthenticated attacker over HTTP and carries a CVSS 3.1 score of 9.3. Oracle warns that the impact can extend beyond OAM itself.

Oracle Access Manager (OAM) is the single sign-on solution of Oracle Fusion Middleware, and the broader Oracle Access Management platform provides authentication, authorization, policy administration, session-related services, logging and auditing. Oracle reports a 2024 Gartner Peer Insights Customers' Choice recognition for Access Management, and a 2025 Oracle article cites an average rating of 4.9 out of 5 across 105 recent reviews with 97% willingness to recommend. These are vendor-reported customer feedback figures, not market share or security measurements. OAM also anchors hybrid identity designs: Oracle documents a federation setup in which Oracle Identity Cloud Service delegates authentication to on-premises OAM, which puts OAM in the dependency chain of cloud applications as well.

Technical Information

What Oracle has disclosed

Oracle describes CVE-2026-91507 as an "easily exploitable" vulnerability in the Authentication Engine component of Oracle Access Manager. The Authentication Engine is the part of OAM that checks credentials and decides who gets a session. The confirmed attack path is network access via HTTP by an unauthenticated attacker, and Oracle's risk matrix lists the issue as remotely exploitable without authentication.

The published vector is CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:H/A:N. Read against the FIRST CVSS v3.1 specification, it breaks down as follows:

MetricValueMeaning
Attack VectorNetworkThe attack is delivered over the network.
Attack ComplexityLowNo specialized conditions beyond the attacker's control are required.
Privileges RequiredNoneNo account or prior access is needed.
User InteractionNoneNo other user has to take any action.
ScopeChangedImpact can extend beyond the security scope of OAM itself.
ConfidentialityLowUnauthorized read access affects a subset of OAM-accessible data.
IntegrityHighUnauthorized creation, deletion or modification can affect critical data or all OAM-accessible data.
AvailabilityNoneNo availability impact is assigned.

Impact: data modification is confirmed, code execution is not

Successful exploitation can give an attacker unauthorized creation, deletion or modification access to critical data or all Oracle Access Manager accessible data, plus unauthorized read access to a subset of that data. Oracle also states that attacks "may significantly impact additional products", which is what the S:C scope change captures. That fits OAM's role. Many applications delegate sign-in to it, so altered OAM data can matter well outside OAM.

The record does not establish remote code execution, operating system command execution, unrestricted data theft or denial of service. The published impact assessment is specifically C:L/I:H/A:N, and Oracle does not name a downstream product or exploit chain.

What remains undisclosed

The primary record provides no CWE identifier, vulnerable function, HTTP endpoint, request format, payload or reproducible exploitation sequence. Third-party aggregators have applied labels: VulDB calls it "improper authorization" and TheHackerWire calls it "Authentication Bypass". Neither label is backed by a primary technical explanation, so we treat the root cause as unknown. Oracle does not publish source code, commits or diffs for Access Manager, so there is no public code change to analyze. Its disclosure policy also withholds technical specifics beyond the advisory and patch materials.

Attack flow based on the published preconditions

Because the mechanism is undisclosed, the attack flow we can responsibly describe stops at what the CVSS vector and Oracle's description establish:

  1. An attacker with network reachability to an OAM deployment's HTTP interface, and no OAM credentials, targets the Authentication Engine.
  2. The attacker interacts with the engine over HTTP. No specialized conditions are required (AC:L) and no victim needs to click or log in (UI:N).
  3. On success, the attacker can create, delete or modify critical OAM data, or all OAM-accessible data, and read a subset of it.
  4. Because the scope is changed, the consequences can reach products that rely on OAM. Architecturally, Oracle documents WebGate as an HTTP request filter registered with Access Manager, and it documents cloud applications that delegate authentication to OAM through Identity Cloud Service. This explains why the scope change matters. It is not evidence that WebGate is the vulnerable component or that these integrations have been exploited.

Exploitation status

The sources we reviewed do not confirm exploitation in the wild. TheHackerWire reported no exploitation reports as of 17 November 2026, no confirmed public exploit code and no known ransomware campaign. The CVE is absent from the CISA Known Exploited Vulnerabilities feed snapshot released 17 November 2026 at 17:53:15 UTC, and Rapid7 marks its KEV field as false. No threat actor has been named. None of this proves attacks are not occurring, and the 9.3 base score describes severity rather than exploit maturity.

Patch Information

The fix ships in Oracle's November 2026 Critical Security Patch Update. Oracle released it on 17 November 2026, and the risk matrix lists CVE-2026-91507 under Oracle Fusion Middleware. That listing is Oracle's own confirmation that this release fixes the flaw.

Oracle's risk matrix entry:

  • Product / component: Oracle Access Manager / Authentication Engine
  • Protocol: HTTP
  • Remote exploit without auth: Yes
  • CVSS 3.1: 9.3 (AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:H/A:N)
  • Fixed release lines: 12.2.1.4.0 and 14.1.2.1.0

What the fix covers. Oracle doesn't publish source code, commits or diffs for Access Manager, so all we know about the fix is what the advisory says. The patch changes how the Authentication Engine behaves, so treat it as a change to your identity infrastructure rather than a routine library update.

How to get it. Oracle's advisory doesn't link to downloads directly. It points to two My Oracle Support Patch Availability Documents instead:

  • CPU450 (Fusion Middleware): lists the exact patch numbers for each affected OAM release line, with installation instructions.
  • CPU433: the Executive Summary and Analysis document for this patch cycle.

The advisory is public, but the patch documents and downloads require a valid Oracle support account. Use CPU450 to match the correct patch to your installed version (12.2.1.4.0 or 14.1.2.1.0). Don't assume one patch covers both.

Other Access Manager fixes in the same release. The November 2026 update covers 13 other Access Manager CVEs besides this one:

  • CVE-2026-114835
  • CVE-2026-91498
  • CVE-2026-91500
  • 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

Applying the OAM patch from this release should close those 13 as well as CVE-2026-91507.

How this release type fits in. Oracle describes Critical Security Patch Updates (CSPUs) as smaller, targeted security releases that complement the cumulative quarterly Critical Patch Updates (CPUs) rather than replacing them. Applying the November CSPU doesn't free you from the regular quarterly CPU cycle. Oracle's guidance is to stay on actively supported versions and apply security patches "without delay".

Interim measures. Oracle's advisory mentions temporarily blocking protocols required by an attack as a general risk-reduction step while patching is pending. For this CVE that protocol is HTTP, which OAM needs to function, and no endpoint restriction or configuration change has been published as a validated workaround. Oracle advises testing such changes on nonproduction systems, and they do not correct the underlying defect. Oracle's advice on removing unnecessary privileges does not apply here, since the vector specifies PR:N.

Fix status still differs between sources. NVD currently returns "CVE ID Not Found" for this ID, and at least one third-party CVE aggregator still shows "No fix available yet". Both are lagging behind Oracle. Use Oracle's November 2026 CSPU advisory as the authoritative record of the fix.

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: network access to OAM via HTTP, with no authentication or user interaction required

Oracle provides security patches only for versions covered by Premier Support or Extended Support. Unsupported releases are not tested, and their absence from the risk matrix does not establish that they are unaffected. Both listed versions are supported releases, so running a supported version does not by itself make a deployment safe. The applicable November 2026 patch must be installed.

Vendor Security History

OAM has a prior, unrelated vulnerability with confirmed exploitation. Belgium's Centre for Cybersecurity warned on 30 November 2022 that CVE-2021-35587, a flaw in the OpenSSO component of OAM, was being actively exploited. That issue allowed unauthenticated HTTP compromise, arbitrary code execution and creation of privileged users, and Oracle had shipped its fix in the January 2022 update. The lesson from that case is the gap between patch availability and the exploitation warnings.

CVE-2021-35587 and CVE-2026-91507 share a product and HTTP exposure, but they affect different components and carry different published impact assessments. The older case tells us nothing about the mechanism or exploitation status of the new one. Oracle itself states that attackers have succeeded against customers who failed to apply available patches, and it directs customers who missed earlier updates to review previous CPU and CSPU advisories.

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