# CVE-2026-34283: Open redirect in Oracle Identity Manager

> Unauthenticated attackers can exploit an open redirect in Oracle Identity Manager to access or modify data, requiring user interaction.

- **Severity:** Medium 6.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 21 Apr 2026
- **Updated:** 22 Apr 2026
- **Also known as:** GHSA-6pjm-v57q-8qfm

## What is CVE-2026-34283?

CVE-2026-34283 is a medium-severity vulnerability in Oracle Identity Manager, published on 21 Apr 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Vulnerability in the Oracle Identity Manager product of Oracle Fusion Middleware (component: Identity Console).  Supported versions that are affected are 12.2.1.4.0 and  14.1.2.0.0. Easily exploitable vulnerability allows unauthenticated attacker with network access via HTTP to compromise Oracle Identity Manager.  Successful attacks require human interaction from a person other than the attacker and while the vulnerability is in Oracle Identity Manager, attacks may significantly impact additional products (scope change). Successful attacks of this vulnerability can result in  unauthorized update, insert or delete access to some of Oracle Identity Manager accessible data as well as  unauthorized read access to a subset of Oracle Identity Manager accessible data. CVSS 3.1 Base Score 6.1 (Confidentiality and Integrity impacts).  CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N).

Weakness: CWE-601 (URL Redirection to Untrusted Site), CWE-284 (Improper Access Control)

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

It affects 1 product.


Products: Oracle Identity Manager.

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

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

## Is CVE-2026-34283 being exploited?

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

## Other vulnerabilities in Oracle Identity Manager

- [CVE-2025-61757](https://insights.sbomify.com/CVE-2025-61757/): Oracle Fusion Middleware Missing Authentication for Critical Function (critical 9.8, exploited in the wild)
- [CVE-2017-10151](https://insights.sbomify.com/CVE-2017-10151/): Auth bypass in Identity Manager (critical 10.0)
- [CVE-2026-60720](https://insights.sbomify.com/CVE-2026-60720/): Auth bypass in Oracle Identity Manager (critical 9.9)
- [CVE-2026-61066](https://insights.sbomify.com/CVE-2026-61066/): Auth bypass in Oracle Identity Manager (critical 9.9)
- [CVE-2026-35268](https://insights.sbomify.com/CVE-2026-35268/): Auth bypass in Identity Manager (critical 9.9)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-34283 is a medium-severity vulnerability in Oracle Identity Manager, published on 21 Apr 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-34283 in the wild and no public exploit code.

Affected product: Oracle Identity Manager. 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-34283/ (Markdown: https://insights.sbomify.com/CVE-2026-34283/index.md)
```

## Sources

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

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