dbcve.org
Unified DirectoryApplication · Oracle

CVE-2026-46776

HIGH · 8.6 CVSS v3.1 Published 2026-06-17
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges 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 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. Successful attacks of this vulnerability can result in unauthorized creation, deletion or modification access to critical data or all Oracle Unified Directory accessible data as well as unauthorized read access to a subset of Oracle Unified Directory accessible data and unauthorized ability to cause a partial denial of service (partial DOS) of Oracle Unified Directory. CVSS 3.1 Base Score 8.6 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:L).

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 · high confidence

This is an unauthenticated LDAP vulnerability in Oracle Unified Directory's OUD Core component affecting versions 12.2.1.4.0 and 14.1.2.1.0. An attacker with network access to LDAP can achieve high-integrity impact (unauthorized create/delete/modify of critical data), low confidentiality impact (read access to subset of data), and low availability impact (partial DOS). The CVSS vector indicates a network-based, low-complexity attack requiring no authentication or user interaction.

MitigationApply Oracle Critical Patch Update (CPU) containing the fix for this vulnerability. If immediate patching is not possible, restrict LDAP network access to trusted clients only using firewall rules or OUD access control rules.

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
Unified DirectoryApplication
Affected:= 12.2.1.4.0= 14.1.2.1.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
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
High
Availability
Low

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

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. Confirm Oracle Unified Directory installation
    Locate OUD installation directory - typically under $ORACLE_HOME/oud or search for 'oud' binary using 'which oud' or 'find /u01 -name oud 2>/dev/null'
    Affected if OUD is not installed on the system
  2. Identify installed OUD version
    Run OUD version command if available, or check Oracle inventory at $ORACLE_HOME/oraInventory/ContentsXML/inventory.xml, or use 'opatch lsinventory' from OUD ORACLE_HOME
    Affected if Installed version matches 12.2.1.4.0 or 14.1.2.1.0 exactly
  3. Verify LDAP listener is active
    Check for LDAP port listening - run 'netstat -tlnp | grep -E "(389|1389)"' or 'ss -tlnp | grep -E "(389|1389)"'
    Affected if LDAP port (389/1389) is open and listening
  4. Determine if LDAP is network accessible
    Review firewall rules ('iptables -L' or 'firewall-cmd --list-all') and OUD network configuration to see if LDAP port accepts external connections
    Affected if LDAP port is reachable from untrusted networks
  5. Test for anonymous LDAP bind
    Use ldapsearch with no credentials: 'ldapsearch -h <oud_host> -p 389 -D "" -b "" -s base "objectclass=*"'
    Affected if Anonymous (unauthenticated) LDAP bind succeeds without credentials

System is affected if OUD versions 12.2.1.4.0 or 14.1.2.1.0 are installed AND the LDAP listener is network-accessible AND anonymous LDAP bind is allowed.

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 Critical Patch Update (CPU) containing the fix for this vulnerability. If immediate patching is not possible, restrict LDAP network access to trusted clients only using firewall rules or OUD access control rules.

Fix this in Unified Directory Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing10.0 h
  • Review / QA6.0 h
34.0 hours of engineering $5,940
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-46776 — 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-46776 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