dbcve.org
Identity ManagerApplication · Oracle

CVE-2026-35294

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 Connector product of Oracle Fusion Middleware (component: Mainframe Connectors). 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 HTTP to compromise Identity Manager Connector. While the vulnerability is in Identity Manager Connector, attacks may significantly impact additional products (scope change). Successful attacks of this vulnerability can result in takeover of Identity Manager Connector. 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 · high confidence

Oracle Identity Manager Connector has a critical vulnerability in the Mainframe Connectors component that allows a low-privileged attacker with network access via HTTP to achieve complete takeover of the Identity Manager Connector. The CVSS 9.9 score with scope change indicates the compromise may propagate to additional products in the Oracle Fusion Middleware environment.

MitigationApply Oracle security patches for versions 12.2.1.4.0 and 14.1.2.1.0 as soon as Oracle releases them. In the interim, restrict network access to Identity Manager Connector systems and monitor for unusual HTTP traffic patterns.

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. Identify Oracle Identity Manager version
    Check the installed version of Oracle Identity Manager by reviewing the Oracle inventory file (ORACLE_HOME/inventory/ContentsXML/oraclehome.xml) or by querying the MBean org.oracle.idm:id=Version through the WebLogic Administration Console
    Affected if The installed version matches 12.2.1.4.0 or 14.1.2.1.0 exactly (note: exact version match required based on affected versions listed)
  2. Verify Mainframe Connectors component status
    Review the Oracle Identity Manager deployment configuration to determine if the Mainframe Connectors module is deployed and active. Check through the WebLogic Administration Console under Deployments or examine the connector configuration files in the OIM_HOME/connectors directory
    Affected if Mainframe Connectors component is deployed and running on the affected version
  3. Assess network exposure of Identity Manager Connector
    Review network configuration and firewall rules to determine if the Identity Manager Connector is accessible via HTTP from untrusted networks. Check listener configurations and exposed endpoints
    Affected if Connector is reachable via HTTP from network segments outside the trusted zone
  4. Review HTTP access logs for suspicious patterns
    Examine HTTP access logs for the Identity Manager Connector (typically found in WebLogic logs directory) for unusual request patterns, especially from low-privileged accounts or unexpected source IP addresses
    Affected if Unusual HTTP traffic patterns detected, particularly requests targeting mainframe connector endpoints from unexpected sources

A system is affected if it runs Oracle Identity Manager version 12.2.1.4.0 or 14.1.2.1.0 with the Mainframe Connectors component enabled and exposed to network access

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 security patches for versions 12.2.1.4.0 and 14.1.2.1.0 as soon as Oracle releases them. In the interim, restrict network access to Identity Manager Connector systems and monitor for unusual HTTP traffic patterns.

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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