Skip to main content
Vulnerability Database/CVE-2026-91259

CVE-2026-91259: Oracle Identity Manager Privilege Escalation

CVE-2026-91259 is a privilege escalation vulnerability in Oracle Identity Manager that enables low-privileged attackers to gain complete system control. This article covers technical details, affected versions, and mitigation.

Published:

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

CVE-2026-91259 Overview

CVE-2026-91259 is a high-severity vulnerability in the Oracle Identity Manager (OIM) product of Oracle Fusion Middleware. The flaw resides in the OIM Legacy UI component and affects supported versions 12.2.1.4.0 and 14.1.2.1.0. A low-privileged attacker with network access over HTTP can exploit this vulnerability without user interaction. Successful exploitation results in complete takeover of Oracle Identity Manager, compromising confidentiality, integrity, and availability. Oracle disclosed the issue in the October 2026 Critical Patch Update.

Critical Impact

An authenticated attacker with low privileges can take over Oracle Identity Manager remotely over HTTP, gaining full control of the identity management plane.

Affected Products

  • Oracle Identity Manager 12.2.1.4.0
  • Oracle Identity Manager 14.1.2.1.0
  • Oracle Fusion Middleware (OIM Legacy UI component)

Discovery Timeline

  • 2026-10-20 - CVE-2026-91259 published to NVD
  • 2026-10-21 - Last updated in NVD database
  • October 2026 - Addressed in Oracle Critical Patch Update

Technical Details for CVE-2026-91259

Vulnerability Analysis

The vulnerability exists in the OIM Legacy UI, a web-facing component of Oracle Identity Manager that handles identity administration workflows. An attacker holding any low-privileged OIM account can send crafted HTTP requests to the Legacy UI and escalate to full application takeover. Because OIM manages provisioning, access control, and credentials across downstream systems, a successful compromise cascades into every integrated application and directory.

The attack requires only network reachability to the OIM HTTP endpoint and a valid low-tier credential. No user interaction is needed, and exploit complexity is low, which makes this flaw practical for both external attackers who have phished a basic account and internal actors.

Root Cause

Oracle has not published root-cause details beyond the component identification. The flaw is isolated to the OIM Legacy UI module and permits a low-privileged session to perform actions outside its authorization boundary. The scope remains unchanged, indicating the impact is contained within the Oracle Identity Manager security authority rather than spreading to the host operating system.

Attack Vector

Exploitation occurs over the network using HTTP against the OIM Legacy UI. The attacker authenticates with a low-privileged account and submits crafted requests that bypass intended authorization checks, resulting in takeover of the OIM instance. See the Oracle Security Alert - October 2026 for vendor remediation details.

Detection Methods for CVE-2026-91259

Indicators of Compromise

  • Unexpected administrative role grants, policy modifications, or user provisioning actions originating from low-privileged OIM accounts.
  • Anomalous HTTP POST or GET requests targeting Legacy UI endpoints under the OIM web application context.
  • New or modified OIM scheduled tasks, event handlers, or adapter configurations that were not deployed through change management.
  • Sudden credential resets or entitlement grants to downstream connected systems issued by OIM outside normal workflow approvals.

Detection Strategies

  • Review OIM audit logs for authorization decisions where a low-privileged user successfully performed admin-tier operations.
  • Correlate web server access logs with OIM application logs to identify request sequences that precede privilege changes.
  • Baseline normal Legacy UI traffic patterns and alert on volumetric or structural deviations per account.
  • Enable WebLogic access logging on the OIM managed server and forward to a SIEM for retention and analytics.

Monitoring Recommendations

  • Ingest OIM, WebLogic, and reverse-proxy logs into a centralized analytics platform for cross-source correlation.
  • Monitor Oracle Database audit trails for the OIM schema to detect direct manipulation of identity tables.
  • Alert on new OIM API clients, OAuth registrations, or trust configurations added after the disclosure date.
  • Track outbound provisioning events from OIM to connected targets and flag bursts outside business hours.

How to Mitigate CVE-2026-91259

Immediate Actions Required

  • Apply the October 2026 Oracle Critical Patch Update to all OIM instances running 12.2.1.4.0 or 14.1.2.1.0.
  • Restrict network access to the OIM Legacy UI to trusted administrative networks and VPN segments until patching is complete.
  • Rotate credentials and session tokens for all OIM accounts, prioritizing privileged and service accounts.
  • Audit recent OIM administrative activity for unauthorized role assignments or policy changes since the publication date.

Patch Information

Oracle addressed CVE-2026-91259 in the October 2026 Critical Patch Update. Administrators should download and apply the patches listed in the Oracle Security Alert - October 2026 for the affected OIM versions. Validate the patch in a staging environment before deploying to production, and schedule emergency change windows given the severity and the identity-plane impact.

Workarounds

  • Place a web application firewall or reverse proxy in front of the OIM Legacy UI and restrict access by source IP and authenticated session attributes.
  • Disable or block routes to the Legacy UI if operations rely exclusively on the modern OIM interface.
  • Enforce multi-factor authentication at the perimeter for every account that can reach the OIM login page.
  • Reduce standing privileges by auditing low-tier OIM roles and removing unused accounts before patch deployment.
bash
# Example: restrict OIM Legacy UI access at the reverse proxy (nginx)
location /oim/faces/ {
    allow 10.10.20.0/24;   # admin jump network
    deny  all;
    proxy_pass http://oim-backend;
}

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

Experience the Most Advanced Cybersecurity Platform

See how the world’s most intelligent, autonomous cybersecurity platform can protect your organization today and into the future.