dbcve.org
Identity ManagerApplication · Oracle

CVE-2026-35268

CRITICAL · 9.9 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 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 Identity Manager product of Oracle Fusion Middleware (component: Core). Supported versions that are affected are 12.2.1.4.0 and 14.1.2.1.0. Easily exploitable vulnerability allows low privileged attacker with network access via T3, IIOP to compromise Identity Manager. While the vulnerability is in Identity Manager, attacks may significantly impact additional products (scope change). Successful attacks of this vulnerability can result in takeover of Identity Manager. CVSS 3.1 Base Score 9.9 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H).

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

Oracle Identity Manager Core component contains a critical vulnerability exploitable via T3/IIOP network protocols. Low-privileged attackers can achieve complete compromise (confidentiality, integrity, availability) of Identity Manager, with potential scope change impacting additional Oracle products.

MitigationApply Oracle patches for versions 12.2.1.4.0 and 14.1.2.1.0 when available; restrict network access to T3/IIOP ports and implement network segmentation to limit exposure.

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
Identity ManagerApplication
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
Low
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

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

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. Verify Oracle Identity Manager installation
    Locate Oracle Identity Manager installation directory and check for OIM core components. Common paths include $ORACLE_HOME/idm/server or check for Oracle Identity Manager processes running (e.g., oim.server, Oracle Identity Manager Application).
    Affected if Oracle Identity Manager is not installed or cannot be found, then not affected by this specific CVE.
  2. Identify installed Oracle Identity Manager version
    Check the version of Oracle Identity Manager. Navigate to the installation directory and look for version files, or use Oracle Enterprise Manager/Admin Console to view the installed version. Common version files are in the config directory or can be retrieved via WLST: getCell().getVersion().
    Affected if The installed version exactly matches 12.2.1.4.0 or 14.1.2.1.0 - only these two specific versions are affected per the CVE.
  3. Confirm T3/IIOP protocol configuration
    Check WebLogic Server configuration for T3/IIOP protocol listeners. Access WebLogic Administration Console, navigate to Domain > Protocols > Channel, or check config.xml for <channel> elements with protocol T3 or IIOP enabled. Also check for IIOP-enabled objects in the JNDI tree.
    Affected if T3 or IIOP protocols are enabled and configured on the WLS server - the vulnerability is exploitable via these network protocols.
  4. Review network exposure of T3/IIOP ports
    Identify ports configured for T3/IIOP (default: T3 on 7001, IIOP on 7002, or custom ports). Check if these ports are exposed to untrusted networks by reviewing firewall rules, load balancer configurations, or exposed network interfaces.
    Affected if T3/IIOP ports are accessible from untrusted networks or the internet, increasing exploitation likelihood.

A user is affected if they have Oracle Identity Manager version 12.2.1.4.0 or 14.1.2.1.0 running with T3/IIOP protocols enabled and accessible on their network.

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 patches for versions 12.2.1.4.0 and 14.1.2.1.0 when available; restrict network access to T3/IIOP ports and implement network segmentation to limit exposure.

Fix this in Identity Manager Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing12.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,760
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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