# CVE-2026-60533: Missing authorization in Oracle Identity Manager Connector

> An unauthenticated attacker on the local network can modify critical data or cause a denial of service in Oracle Identity Manager Connector.

- **Severity:** High 8.0 (`CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:C/C:N/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 21 Jul 2026
- **Updated:** 27 Jul 2026
- **Also known as:** GHSA-wvr5-8gxp-7wm2

## What is CVE-2026-60533?

CVE-2026-60533 is a high-severity missing authorization vulnerability in Oracle Identity Manager Connector, published on 21 Jul 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Vulnerability in the Oracle 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. Difficult to exploit vulnerability allows unauthenticated attacker with access to the physical communication segment attached to the hardware where the Oracle Identity Manager Connector executes to compromise Oracle Identity Manager Connector.  While the vulnerability is in Oracle Identity Manager Connector, attacks may significantly impact additional products (scope change).  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 and unauthorized ability to cause a hang or frequently repeatable crash (complete DOS) of Oracle Identity Manager Connector. CVSS 3.1 Base Score 8.0 (Integrity and Availability impacts).  CVSS Vector: (CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:C/C:N/I:H/A:H).

Weakness: CWE-284 (Improper Access Control)

## Which versions are affected by CVE-2026-60533?

It affects 1 product.


Products: Oracle Identity Manager Connector.

## How do I fix CVE-2026-60533?

No fix has been published for CVE-2026-60533 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-60533 being exploited?

There is no known exploitation of CVE-2026-60533 in the wild and no public exploit code.

## Other vulnerabilities in Oracle Identity Manager Connector

- [CVE-2026-60990](https://insights.sbomify.com/CVE-2026-60990/): Auth bypass in Oracle Identity Manager Connector (critical 9.9)
- [CVE-2026-60995](https://insights.sbomify.com/CVE-2026-60995/): Auth bypass in Oracle Identity Manager Connector (critical 9.9)
- [CVE-2026-60531](https://insights.sbomify.com/CVE-2026-60531/): Auth bypass in Oracle Identity Manager Connector (critical 9.9)
- [CVE-2026-46792](https://insights.sbomify.com/CVE-2026-46792/): Auth bypass in Identity Manager Connector (critical 9.9)
- [CVE-2026-46793](https://insights.sbomify.com/CVE-2026-46793/): Auth bypass in Identity Manager Connector (critical 9.9)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-60533 and fix it if it is affected.

What it is: CVE-2026-60533 is a high-severity missing authorization vulnerability in Oracle Identity Manager Connector, published on 21 Jul 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-60533 in the wild and no public exploit code.

Affected product: Oracle Identity Manager Connector. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-60533/ (Markdown: https://insights.sbomify.com/CVE-2026-60533/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-60533
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-60533
- OSV: https://osv.dev/vulnerability/CVE-2026-60533

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-60533/
Summaries are generated and may contain mistakes; the official description above is the record.