dbcve.org
Identity Manager ConnectorApplication · Oracle

CVE-2026-34294

MEDIUM · 5.9 CVSS v3.1 Published 2026-04-21
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
65/100
Remediation priority · Elevated
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Vulnerability in the Oracle Identity Manager Connector product of Oracle Fusion Middleware (component: Microsoft Active Directory). The supported version that is affected is 12.2.1.4.0. Difficult to exploit vulnerability allows low privileged attacker with network access via LDAP to compromise Oracle Identity Manager Connector. Successful attacks of this vulnerability can result in unauthorized creation, deletion or modification access to critical data or all Oracle Identity Manager Connector accessible data as well as unauthorized read access to a subset of Oracle Identity Manager Connector accessible data. CVSS 3.1 Base Score 5.9 (Confidentiality and Integrity impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:H/A:N).

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

Vulnerability in Oracle Identity Manager Connector for Microsoft Active Directory allows low-privileged attackers with network access via LDAP to achieve unauthorized read access to a subset of data and create/modify/delete access to critical data. The high attack complexity indicates exploitation requires specific conditions.

MitigationApply Oracle's patch for version 12.2.1.4.0; restrict LDAP network access to trusted sources and ensure AD service accounts follow least privilege principles.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Identity Manager ConnectorApplication
Affected:= 12.2.1.4.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
High
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
High
Availability
None

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify Oracle Identity Manager is installed
    Locate the Oracle Identity Manager installation directory or check for OIM-related processes and services running on the system
    Affected if OIM is not present on the system, the CVE does not apply
  2. Identify the connector version
    Navigate to the Oracle Identity Manager connector directory for Active Directory or check the connector's manifest/version file. Typical path patterns include <OIM_HOME>/connector/<version> or check via OIM console under Manage Connector
    Affected if The connector version is exactly 12.2.1.4.0 - only this specific version is affected
  3. Confirm AD connector is configured
    Check if the Active Directory connector is actively configured or deployed within Oracle Identity Manager. Look for AD connector profiles, reconciliation jobs, or provisioning workflows targeting Active Directory
    Affected if The AD connector is not configured or deployed, the specific exploitation path may not be reachable
  4. Assess LDAP network exposure
    Review firewall rules, network ACLs, and LDAP service binding configurations to determine if the Active Directory LDAP port (typically 389 or 636) is accessible from untrusted network segments
    Affected if LDAP is exposed to untrusted network access, enabling the low-privileged network-based attack vector described in the CVE

The environment is affected only if Oracle Identity Manager with the Active Directory connector version exactly 12.2.1.4.0 is installed, the AD connector is actively configured, and LDAP is accessible from untrusted network segments.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply Oracle's patch for version 12.2.1.4.0; restrict LDAP network access to trusted sources and ensure AD service accounts follow least privilege principles.

Fix this in Identity Manager Connector Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing10.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,580
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,928.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-34294 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-34294 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data