Identity ManagerApplication · Oracle

CVE-2026-61196

CRITICAL · 9.8 CVSS v3.1 Published 2026-07-21

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 4 weeks old

Official description

NVD · unedited

Vulnerability in the Oracle 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 HTTP to compromise Oracle Identity Manager. Successful attacks of this vulnerability can result in takeover of Oracle 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

Critical unauthenticated remote code execution vulnerability in Oracle Identity Manager's Legacy UI component. Allows any network attacker to compromise the OIM system via HTTP without credentials, achieving complete confidentiality, integrity, and availability impact (CVSS 9.8). Affects versions 12.2.1.4.0 and 14.1.2.1.0.

MitigationApply Oracle's security patch immediately when available. Until then, restrict network access to OIM Legacy UI through firewalls or network segmentation, and consider disabling the Legacy UI 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 version

Check the installed Oracle Identity Manager version through the administration console or by examining the inventory files in the Oracle Middleware home directory. Common locations include $ORACLE_HOME/oracle_common/modules/oracle.idm_/version.txt or through the Enterprise Manager console.

Affected if The installed version matches exactly 12.2.1.4.0 or 14.1.2.1.0
Locate the Legacy UI component

Identify whether the Legacy UI component is deployed by examining the web application deployment descriptors or the application server console. The Legacy UI is typically accessible via the /identity/legacy or similar legacy endpoint paths.

Affected if The Legacy UI component is present and deployed in the application server
Verify Legacy UI network accessibility

Check network accessible URLs by attempting to access the Legacy UI endpoints from an external host or by reviewing reverse proxy and load balancer configurations that route traffic to the Oracle Identity Manager application.

Affected if The Legacy UI endpoint is reachable over the network without authentication
Review access control policies

Examine the web application firewall rules, Oracle Access Manager policies, or any IP-based restrictions applied to the Legacy UI component to determine if unauthenticated access is permitted.

Affected if No authentication is required to access the Legacy UI component or the component allows anonymous access

Your environment is affected if you are running Oracle Identity Manager version 12.2.1.4.0 or 14.1.2.1.0 with the Legacy UI component enabled and network-accessible without authentication.

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's security patch immediately when available. Until then, restrict network access to OIM Legacy UI through firewalls or network segmentation, and consider disabling the Legacy UI if not required.

Recommended fix Moderate confidence

Oracle CPUs are the primary fix; contact Oracle for version availability beyond 14.1.2.1.0

Contact Oracle Support or access My Oracle Support to obtain the Critical Patch Update (CPU) that addresses CVE-2026-61196 for Oracle Identity Manager
Review the Oracle Critical Patch Update advisory for the specific patch number and download instructions
Apply the appropriate Oracle CPU patch to both affected versions (12.2.1.4.0 and 14.1.2.1.0) following Oracle's patch installation documentation
Restart Oracle Identity Manager services as required by the patch installation
Verify the patch was successfully applied by checking the Oracle Identity Manager version and confirming the vulnerability is resolved
If Legacy UI component is not required in production, consider disabling or restricting access to reduce attack surface

Caveat Apply CPU in test environment first to verify compatibility; Oracle CPUs may require downtime and can introduce regressions

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

Fix this in Identity Manager Scoped from the published advisory

Consultation8.0 h
Implementation16.0 h
Testing24.0 h
Review / QA8.0 h

56.0 hours of engineering $9,520

Get help mitigating

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

Scan for this in your stack

Free · runs locally

dbcve dependency scanner

Check whether your project pulls in CVE-2026-61196 — 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-61196 in production — separate from our analysis above.

Notes0 Guidelines

Know something about CVE-2026-61196?

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 56 hrs · High

Typical engagement from $9,520

Get a fix See the full breakdown ↓

A high-priority vulnerability. Send your environment and a specialist will scope CVE-2026-61196 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