# CVE-2026-60842: Open redirect in Oracle Knowledge Management

> Unauthenticated attackers can exploit an open redirect in Oracle Knowledge Management 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 Jul 2026
- **Updated:** 24 Jul 2026
- **Also known as:** GHSA-j72j-2hvh-wrmg

## What is CVE-2026-60842?

CVE-2026-60842 is a medium-severity vulnerability in Oracle Knowledge Management, published on 21 Jul 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 Knowledge Management product of Oracle E-Business Suite (component: Search).  Supported versions that are affected are 12.2.5-12.2.15. Easily exploitable vulnerability allows unauthenticated attacker with network access via HTTP to compromise Oracle Knowledge Management.  Successful attacks require human interaction from a person other than the attacker and while the vulnerability is in Oracle Knowledge Management, 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 Knowledge Management accessible data as well as  unauthorized read access to a subset of Oracle Knowledge Management 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-352 (Cross-Site Request Forgery), CWE-285 (Improper Authorization)

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

It affects 1 product.


Products: Oracle Knowledge Management.

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

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

## Is CVE-2026-60842 being exploited?

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

## Other vulnerabilities in Oracle Knowledge Management

- [CVE-2021-2198](https://insights.sbomify.com/CVE-2021-2198/): Information disclosure in Knowledge Management (high 8.2)
- [CVE-2020-2841](https://insights.sbomify.com/CVE-2020-2841/): Information disclosure in Knowledge Management (high 8.2)
- [CVE-2019-2660](https://insights.sbomify.com/CVE-2019-2660/): Cross-site scripting in Knowledge Management (high 8.2)
- [CVE-2017-10410](https://insights.sbomify.com/CVE-2017-10410/): Cross-site scripting in Knowledge Management (high 8.2)
- [CVE-2017-10411](https://insights.sbomify.com/CVE-2017-10411/): Cross-site scripting in Knowledge Management (high 8.2)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-60842 is a medium-severity vulnerability in Oracle Knowledge Management, published on 21 Jul 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-60842 in the wild and no public exploit code.

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

## Sources

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

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