dbcve.org
Identity Manager ConnectorApplication · Oracle

CVE-2026-34286

CRITICAL · 9.1 CVSS v3.1 Published 2026-04-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

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 Identity Manager Connector product of Oracle Fusion Middleware (component: Core). The supported version that is affected is 12.2.1.4.0. Easily exploitable vulnerability allows unauthenticated attacker with network access via HTTPS to compromise Oracle Identity Manager Connector. Successful attacks of this vulnerability can result in unauthorized creation, deletion or modification access to critical data or all Oracle Identity Manager Connector accessible data as well as unauthorized access to critical data or complete access to all Oracle Identity Manager Connector accessible data. CVSS 3.1 Base Score 9.1 (Confidentiality and Integrity impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N).

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

This is a critical unauthenticated remote code execution or data manipulation vulnerability in Oracle Identity Manager Connector version 12.2.1.4.0. An attacker with network access via HTTPS can create, delete, or modify critical data, as well as access all data within the connector without any credentials. The CVSS vector indicates a straightforward network attack requiring no privileges or user interaction.

MitigationApply the Oracle security patch for Oracle Identity Manager Connector 12.2.1.4.0 from Oracle Support. If immediate patching is not possible, restrict network access to the connector HTTPS endpoint using firewall rules or network segmentation, and monitor for unauthorized access attempts.

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 Manager ConnectorApplication
Affected:= 12.2.1.4.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
High
Integrity
High
Availability
None

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

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 Connector installation
    Locate the Oracle Identity Manager Connector installation directory and look for version information in manifest files, README, or version.properties. Common paths include the Oracle home directory or connector deployment folders.
    Affected if The installed connector version is exactly 12.2.1.4.0
  2. Verify the exact connector version
    Check the connector's version file, about.html, or use the connector's built-in version check command if available. Compare the reported version against 12.2.1.4.0.
    Affected if The version returned is 12.2.1.4.0 exactly
  3. Confirm HTTPS endpoint exposure
    Determine if the Oracle Identity Manager Connector HTTPS endpoint is accessible from the network. Check firewall rules, load balancer configurations, or test connectivity to the connector's HTTPS port from an external host.
    Affected if The connector's HTTPS port is reachable from untrusted networks without firewall filtering
  4. Verify authentication is not enforced on the endpoint
    Inspect the connector's configuration files or security settings to confirm whether authentication is required for the HTTPS endpoints. Attempt an unauthenticated request to the connector API if safe to do so.
    Affected if The connector accepts requests without requiring authentication credentials

You are affected if Oracle Identity Manager Connector version 12.2.1.4.0 is installed and its HTTPS endpoint is network-accessible without authentication enforcement.

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 the Oracle security patch for Oracle Identity Manager Connector 12.2.1.4.0 from Oracle Support. If immediate patching is not possible, restrict network access to the connector HTTPS endpoint using firewall rules or network segmentation, and monitor for unauthorized access attempts.

Fix this in Identity Manager Connector Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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