LiveActive security incident?Get immediate response
CVE Record

CVE-2026-60360: Vulnerability in the Oracle Unified Directory product of Oracle Fusion Middleware (component: OUD Core).

Vulnerability in the Oracle Unified Directory product of Oracle Fusion Middleware (component: OUD Core). Supported versions that are affected are 12.2.1.4.0 and 14.1.2.1.0. Easily exploitable vulnerability allows unauthenticated attacker with network access via LDAP to compromise Oracle Unified Directory. While the vulnerability is in Oracle Unified Directory, attacks may significantly impact additional products (scope change). Successful attacks of this vulnerability can result in takeover of Oracle Unified Directory. CVSS 3.1 Base Score 10.0 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H).

CriticalCVSS 10Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

This is a critical Oracle Unified Directory flaw. An unauthenticated attacker with LDAP network access can compromise OUD, with possible impact beyond OUD because the CVSS scope changes. Successful exploitation can lead to full takeover, affecting confidentiality, integrity, and availability.

Executive priority

Treat this as an urgent identity-infrastructure risk. Full OUD takeover can undermine authentication, directory integrity, and dependent systems, so patch planning and exposure reduction should be prioritized immediately.

Technical view

CVE-2026-60360 affects Oracle Unified Directory OUD Core versions 12.2.1.4.0 and 14.1.2.1.0. The CVSS 3.1 score is 10.0: network attack vector, low complexity, no privileges, no user interaction, scope changed, and high CIA impact.

Likely exposure

Organizations running Oracle Unified Directory 12.2.1.4.0 or 14.1.2.1.0 with LDAP reachable from untrusted networks are most exposed. Internal-only LDAP still matters because no authentication is required.

Exploitation context

The provided sources say the issue is easily exploitable via LDAP and can result in OUD takeover. They do not state active exploitation, and the CVE is not marked KEV in the bundle.

Researcher notes

No CWE is provided in the bundle, so root cause is not identified here. Analysis should focus on affected OUD versions, LDAP reachability, scope-change implications, and vendor CPU guidance without assuming exploit details.

Mitigation direction

  • Review Oracle's July 2026 Critical Patch Update guidance for this CVE.
  • Apply Oracle-provided fixes for affected OUD versions when available.
  • Restrict LDAP exposure to trusted networks and required clients only.
  • Monitor OUD and LDAP logs for unusual unauthenticated activity.
  • Prioritize compensating controls until vendor remediation is confirmed.

Validation and detection

  • Inventory all Oracle Unified Directory deployments and versions.
  • Confirm whether versions 12.2.1.4.0 or 14.1.2.1.0 are present.
  • Check whether LDAP is reachable from internet or untrusted network segments.
  • Verify Oracle CPU remediation status for each affected instance.
  • Review logs for anomalous LDAP access before and after remediation.
Prepared
Confidence
high
Sources
3

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2026-60360 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Critical
CVSS
10 (3.1)
Known Exploited
No
Published

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

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
3Timeline events
0ADP providers
2Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
10CVSS 3.1CriticalCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H3.96oracle

Vulnerability scoring details

Base CVSS 3.1 score

10Critical
CVSS 3.1 vector shape for CVE-2026-60360Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
Oracle CorporationOracle Unified Directory12.2.1.4.0, 14.1.2.1.0Listed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.