CVE-2026-46794
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 · uneditedVulnerability in the Identity Manager Connector product of Oracle Fusion Middleware (component: Generic Unix Connector). 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 SSH 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 confidenceCritical vulnerability in Oracle Identity Manager Connector's Generic Unix Connector allows low-privileged attackers with network access via SSH to achieve complete takeover of the connector. The CVSS 9.9 score reflects the critical severity given the low attack complexity, changed scope impacting additional products, and total compromise of confidentiality, integrity, and availability.
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= 12.2.1.4.0= 14.1.2.1.0CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify Oracle Identity Manager Connector installationCheck if Oracle Identity Manager Connector is installed on the system. Look for Oracle Fusion Middleware or Oracle Identity Management directory structures, typically under $ORACLE_HOME or /opt/oracle. Search for directories named 'oim' or 'idm' that contain connector-related files.Affected if Oracle Identity Manager Connector is installed and the Generic Unix Connector component is present
-
Determine the installed connector versionLocate version files or manifest files within the Oracle Identity Manager Connector installation. Check for version.properties, manifest.mf, or similar version metadata files in the connector deployment directories. Look specifically for the Generic Unix Connector component version.Affected if The installed version matches exactly 12.2.1.4.0 or 14.1.2.1.0
-
Verify Generic Unix Connector is configuredExamine the connector configuration files for the Generic Unix Connector. Look in the connector's config directory for XML or properties files that define Unix/Linux target system connections. Check for connector configuration XML files with 'GenericUnix' or 'Unix' in the filename or configuration content.Affected if Generic Unix Connector is configured and active for managing Unix/Linux targets
-
Check SSH connectivity configurationReview connector configuration for SSH-based connectivity settings. Examine the connector's IT (Resource Object) configuration in Oracle Identity Manager or the connector's direct configuration files for SSH connection parameters such as host, port, and authentication settings.Affected if SSH network access is enabled as the communication protocol for the connector
-
Review connector deployment artifactsSearch for deployed connector JAR files or deployment descriptors. Look for files named GenericUnixConnector.jar, or similar naming patterns, in the connector libraries directory. Check deployment descriptors that reference the vulnerable component.Affected if Generic Unix Connector JAR files for the affected versions are deployed
A user is affected if Oracle Identity Manager Connector with Generic Unix Connector is installed, the version is exactly 12.2.1.4.0 or 14.1.2.1.0, and SSH-based connectivity to Unix/Linux target systems is configured or enabled.
Generated from the published advisory. Verify against your own configuration.
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 dataApply Oracle patches for versions 12.2.1.4.0 and 14.1.2.1.0 immediately. Restrict SSH access to the connector using network segmentation and follow least-privilege principles for connector service accounts.
- Consultation6.0 h
- Implementation12.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,448.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-46794 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-46794 in production — separate from our analysis above.
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.
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.
- 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