Identity ManagerApplication · Oracle

CVE-2026-46807

CRITICAL · 9.8 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 →

100/100

Remediation priority · Urgent

Remotely reachable No privileges Zero-click

Official description

NVD · unedited

Vulnerability in the Identity Manager product of Oracle Fusion Middleware (component: OIM Legacy UI). 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 T3, IIOP to compromise Identity Manager. Successful attacks of this vulnerability can result in takeover of Identity Manager. CVSS 3.1 Base Score 9.8 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H).

Technical summary

dbcve analysis · high confidence

Unauthenticated remote code execution vulnerability in Oracle Identity Manager's Legacy UI component. Attackers with network access via T3 or IIOP protocols can exploit this flaw without any credentials, achieving complete system takeover of the Identity Manager instance.

MitigationApply Oracle security patches for the affected versions (12.2.1.4.0, 14.1.2.1.0). As an immediate workaround, restrict network access to T3 and IIOP ports or disable the Legacy UI component if not required.

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

Affected products & versions

NVD · CPE data

Identity ManagerApplication

Affected:= 12.2.1.4.0= 14.1.2.1.0

CVSS breakdown

From the vector

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

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

Am I affected?

dbcve checks

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

Identify Oracle Identity Manager installation and version

Check the OIM installation directory for version files, or run: java -jar $ORACLE_HOME/wlsserver_12.2.1.4.0/bin/wlsversion.jar or check the inventory file $ORACLE_HOME/inventory/ContentsXML/comps.xml

Affected if The installed version matches exactly 12.2.1.4.0 or 14.1.2.1.0
Determine if Legacy UI component is enabled

Check the WebLogic console or config.xml for the Legacy UI application deployment status. Look for deployments named 'oim-legacy-ui' or similar Legacy UI related components under Deployments in the WLS console.

Affected if The Legacy UI application is deployed and in an Active state
Verify T3 protocol listener configuration

Check WebLogic Server configuration for T3 listeners: inspect the $DOMAIN_HOME/config/config.xml file for <network-access-point> entries with T3 protocol, or view Server > Protocols > T3 in the WebLogic Admin Console.

Affected if T3 protocol is enabled and listening on any network interface accessible from untrusted networks
Verify IIOP protocol listener configuration

Inspect config.xml for IIOP <network-access-point> entries, or view Server > Protocols > IIOP in the WebLogic Admin Console.

Affected if IIOP protocol is enabled and accessible from untrusted networks
Confirm network accessibility of exploitation vectors

Scan network ports or review firewall rules to determine if ports commonly used for T3 (7001 default) and IIOP (7002 default) are exposed to untrusted network segments.

Affected if T3 or IIOP ports are reachable from network segments without proper access controls

A user is affected if their Oracle Identity Manager version is exactly 12.2.1.4.0 or 14.1.2.1.0 AND the Legacy UI component is enabled AND T3 or IIOP protocols are network-accessible from untrusted sources.

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

Remediation

dbcve · scoped

Mitigation available No clean upgrade yet — mitigate in the meantime

Mitigation

Apply Oracle security patches for the affected versions (12.2.1.4.0, 14.1.2.1.0). As an immediate workaround, restrict network access to T3 and IIOP ports or disable the Legacy UI component if not required.

Recommended fix Moderate confidence

Oracle Identity Manager 12.2.x or 14.1.x (latest supported version per Oracle's lifecycle documentation)

Check Oracle's Critical Patch Update advisory for CVE-2026-46807 at oracle.com/security-alerts to obtain the specific patch for your version
For Identity Manager 12.2.1.4.0: Apply the latest security patch from Oracle's Critical Patch Update that addresses this vulnerability
For Identity Manager 14.1.2.1.0: Apply the latest security patch from Oracle's Critical Patch Update that addresses this vulnerability
Alternatively, upgrade to a newer supported Oracle Identity Manager version if available
After patching, verify the OIM Legacy UI component is no longer accessible without authentication

Caveat Review Oracle's patch readme for any post-installation requirements or configuration changes needed after applying the security patch

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Identity Manager Scoped from the published advisory

Consultation12.0 h
Implementation20.0 h
Testing24.0 h
Review / QA12.0 h

68.0 hours of engineering $11,760

Get help mitigating

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

Scan for this in your stack

Free · runs locally

dbcve dependency scanner

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

Primary sources

www.oracle.comVendor Advisory
nvd.nist.govNVD record

Practitioner notes

Contributed

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

Notes0 Guidelines

Know something about CVE-2026-46807?

The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.

The version that genuinely resolved it — not the one the vendor claimed
A config change or rule that shut the vector down
A gotcha in the upgrade path that cost you an afternoon

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

At a glance

A fix existsA vendor remedy is published

Severity 9.8 Critical

Exploit likelihood EPSS, next 30 days 0.5%

Affects: Identity Manager

Remediation

A high-priority fix

Fix this in Identity Manager 68 hrs · High

Typical engagement from $11,760

Get a fix See the full breakdown ↓

A high-priority vulnerability. Send your environment and a specialist will scope CVE-2026-46807 and return a fixed quote and timeline.

You’ll deal with our team directly and deploy the reviewed fix to staging first — never straight to production.

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.

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.

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.

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.

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.

Check your environment

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.

Scan for this in your stack

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

Practitioner notes

No notes yet

Official description

Technical summary

Affected products & versions

CVSS breakdown

Am I affected?

Remediation

References