Automated Threat Modeling

Brief Summary: CVE-2026-34287 — Unauthenticated Data Access in Oracle Identity Manager Connector Core Component

A short review of CVE-2026-34287, a CVSS 9.1 vulnerability in Oracle Identity Manager Connector that lets unauthenticated attackers read and modify critical identity data over HTTPS. Covers patch information and affected versions.

CVE Analysis

6 min read

ZeroPath CVE Analysis
ZeroPath CVE Analysis

2026-04-21

Brief Summary: CVE-2026-34287 — Unauthenticated Data Access in Oracle Identity Manager Connector Core Component
Experimental AI-Generated Content

This CVE analysis is an experimental publication that is completely AI-generated. The content may contain errors or inaccuracies and is subject to change as more information becomes available. We are continuously refining our process.

If you have feedback, questions, or notice any errors, please reach out to us.

[email protected]

Introduction

An unauthenticated attacker who can reach Oracle Identity Manager Connector over HTTPS can silently read, modify, and delete critical identity data managed by the platform, with no credentials and no user interaction. CVE-2026-34287, disclosed in Oracle's April 2026 Critical Patch Update, carries a CVSS 3.1 base score of 9.1. It is one of a cluster of six related vulnerabilities patched at the same time in the same component.

Oracle Identity Manager Connector is a component of Oracle Fusion Middleware that integrates Oracle Identity Manager (OIM) with external target systems such as directories, databases, and enterprise applications. It is widely deployed in large enterprises that rely on Oracle's identity governance stack to manage user provisioning, access requests, and compliance workflows. Compromising this connector layer can undermine the trust model of an organization's entire identity infrastructure.

Technical Information

CVE-2026-34287 affects the Core component of Oracle Identity Manager Connector version 12.2.1.4.0 within Oracle Fusion Middleware. The CVSS 3.1 vector is AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N.

CVSS Vector Breakdown

MetricValueMeaning
Attack Vector (AV)NetworkExploitable remotely over HTTPS
Attack Complexity (AC)LowNo special conditions or race conditions required
Privileges Required (PR)NoneNo authentication needed
User Interaction (UI)NoneNo victim action required
Scope (S)UnchangedImpact confined to the vulnerable component
Confidentiality (C)HighFull read access to critical data
Integrity (I)HighAbility to create, modify, or delete critical data
Availability (A)NoneNo denial of service impact

No required privileges, no user interaction, and low attack complexity over a network vector together make this vulnerability particularly dangerous. An attacker needs only HTTPS reachability to the Connector's Core endpoints.

Root Cause Analysis

Oracle has not disclosed granular technical details, which is its standard practice for CPU patches. Even so, the vulnerability profile strongly indicates that authentication and authorization enforcement is missing or broken on HTTPS endpoints exposed by the Connector's Core request-handling path. Because exploitation requires no privileges, certain endpoints were accessible to completely unauthenticated callers, who could both read and write critical identity data.

Attack Flow

Based on the advisory details, the exploitation path follows this sequence:

  1. The attacker identifies a network-reachable Oracle Identity Manager Connector instance (version 12.2.1.4.0) exposed over HTTPS.
  2. The attacker sends crafted HTTPS requests to the Connector's Core component endpoints that lack proper authentication checks.
  3. Without providing any credentials, the attacker can read all data accessible to the Connector, including critical identity and provisioning information.
  4. The attacker can also create, modify, or delete critical data through the same unauthenticated access path.
  5. Because the availability impact is None, the system keeps operating normally, so availability monitoring alone is unlikely to detect the attack.

Oracle patched a cluster of six related vulnerabilities in the same CPU, all targeting the Oracle Identity Manager Connector 12.2.1.4.0 Core component over HTTPS:

CVE IdentifierComponentProtocolCVSS Score
CVE-2026-34285CoreHTTPS9.1
CVE-2026-34286CoreHTTPS9.1
CVE-2026-34287CoreHTTPS9.1
CVE-2026-34288 through CVE-2026-34290CoreHTTPSPatched in same CPU
CVE-2026-34294CoreHTTPSPatched in same CPU

The clustering suggests that Oracle performed a focused security review of this integration component and found multiple distinct flaws in the same area.

Patch Information

Oracle fixed CVE-2026-34287 in the April 2026 Critical Patch Update (CPU), released on April 21, 2026. This CPU is a large batch update with 483 new security patches across Oracle's products.

The patch remediates the network-accessible flaw in the Core component of Oracle Identity Manager Connector 12.2.1.4.0 that previously allowed an unauthenticated attacker to read and modify critical data over HTTPS. Based on the advisory's risk matrix entry, the fix almost certainly tightens authentication or authorization enforcement in the Connector's Core request-handling path. HTTPS endpoints that previously lacked proper access controls would then require valid credentials or tokens before serving or accepting data.

Oracle Identity Manager Connector is a closed-source, proprietary product, so no public commit diff or open-source changeset is available. Oracle distributes the binary patch exclusively through its My Oracle Support (MOS) portal, and only customers with active support contracts can access it. Oracle deliberately withholds implementation specifics to shrink the window in which attackers could reverse-engineer the fix before customers have applied it.

To apply this patch: administrators should log into My Oracle Support, locate the April 2026 CPU patches for Oracle Fusion Middleware (specifically Oracle Identity Manager Connector 12.2.1.4.0), and follow Oracle's standard CPU application procedures. Given the CVSS 9.1 severity, and given that exploitation needs no user interaction or privileges, administrators should prioritize this patch for immediate deployment.

For organizations that cannot patch immediately, Oracle recommends blocking network access to the Connector's HTTPS endpoints as the most effective interim control. Since the vulnerability requires no privileges to exploit, network-level isolation works better than access-control adjustments within the application. Oracle strongly recommends testing any interim changes on non-production systems first, because restricting HTTPS access may break application functionality.

Affected Systems and Versions

The only confirmed affected configuration is:

  • Product: Oracle Identity Manager Connector
  • Parent Suite: Oracle Fusion Middleware
  • Component: Core
  • Affected Version: 12.2.1.4.0
  • Protocol: HTTPS

Organizations running Oracle Identity Manager Connector version 12.2.1.4.0 with the Core component accessible over HTTPS are vulnerable. The advisory does not list any other versions as affected.

Vendor Security History

Oracle runs one of the most structured security patching programs in the enterprise software industry and releases Critical Patch Updates quarterly. The April 2026 CPU alone contained 483 new security patches. When warranted, Oracle also issues out-of-band Security Alerts. A March 20, 2026 alert, for example, addressed Oracle Identity Manager and Oracle Web Services Manager.

Oracle has publicly acknowledged that it "continues to periodically receive reports of attempts to maliciously exploit vulnerabilities for which Oracle has already released security patches," and that "in some instances, attackers have been successful because targeted customers had failed to apply available Oracle patches." Timely patching matters, particularly for vulnerabilities with a CVSS score of 9.1 that require no authentication to exploit.

Six related CVEs in the same component within a single CPU suggest that Oracle conducted a thorough internal review of the Identity Manager Connector's Core component. If so, that is a good sign of proactive security investment in this area.

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