Oracle Unified Directory EUVD-2026-46825

Exploitation requires network access to the Oracle Unified Directory LDAP interface on OUD Core 12.2.1.4.0 or 14.1.2.1.0; per the CVSS vector (PR:N/UI:N) it is unauthenticated and needs no user interaction. The dominant limiting factor is high attack complexity (AC:H) - Oracle explicitly labels it 'difficult to exploit,' meaning the attacker must meet conditions beyond their direct control (such as specific server state, configuration, or timing) rather than sending a single trivial request. Exposure is further limited to environments where the OUD LDAP listener is network-reachable by the attacker; deployments that isolate the directory behind strict network segmentation substantially reduce reachability. The scope change (S:C) means a successful bypass can extend impact to other products that rely on this directory.

The CVSS 3.1 base score of 8.7 (High) is driven by network vector (AV:N), no privileges (PR:N), no user interaction (UI:N), a scope change (S:C), and high confidentiality and integrity impact - partially offset by high attack complexity (AC:H), which Oracle describes as 'difficult to exploit.' AC:H is the key mitigating signal: it implies the attacker needs conditions outside their control (specific timing, configuration, or preparatory work) rather than a trivial single-shot request. There is no CISA KEV listing and no public proof-of-concept in the provided intelligence, and no EPSS score was supplied, so real-world exploitation probability cannot be quantified from this data. On balance this is a genuine priority for organizations running OUD as an authentication authority - the scope change and authentication-bypass tag mean a compromise can cascade into dependent applications - but the high complexity and absence of known exploitation suggest it is not yet a mass-exploitation threat. Note a tension worth verifying with Oracle: the 'Authentication Bypass' tag suggests conceptual ease, while AC:H asserts difficulty; reconcile these before deprioritizing.

An attacker with only network reach to the OUD LDAP endpoint crafts a specialized sequence of LDAP requests that abuses the OUD Core authentication/authorization handling to bypass access controls, then reads and modifies critical directory data such as account entries and privileges. Leveraging the scope change, the attacker uses the altered directory data to gain unauthorized access to downstream applications that trust OUD for identity. Exploitation requires satisfying high-complexity preconditions (AC:H) and no public proof-of-concept is currently known, making this a targeted rather than opportunistic scenario.