# CVE-2026-60918: Privilege escalation in Oracle Shipping Execution

> High-privileged attackers can compromise Oracle Shipping Execution via HTTP, leading to full system takeover.

- **Severity:** High 7.2 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 21 Jul 2026
- **Updated:** 24 Jul 2026
- **Also known as:** GHSA-569f-rxfw-jqr4

## What is CVE-2026-60918?

CVE-2026-60918 is a high-severity vulnerability in Oracle Shipping Execution, published on 21 Jul 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Vulnerability in the Oracle Shipping Execution product of Oracle E-Business Suite (component: Internal Operations).  Supported versions that are affected are 12.2.12-12.2.15. Easily exploitable vulnerability allows high privileged attacker with network access via HTTP to compromise Oracle Shipping Execution.  Successful attacks of this vulnerability can result in takeover of Oracle Shipping Execution. CVSS 3.1 Base Score 7.2 (Confidentiality, Integrity and Availability impacts).  CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H).

Weakness: CWE-284 (Improper Access Control), CWE-306 (Missing Authentication for Critical Functionality), CWE-269 (Improper Privilege Management)

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

It affects 1 product.


Products: Oracle Shipping Execution.

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

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

## Is CVE-2026-60918 being exploited?

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

## Other vulnerabilities in Oracle Shipping Execution

- [CVE-2021-35563](https://insights.sbomify.com/CVE-2021-35563/): Missing authorization in Shipping Execution (high 8.1)
- [CVE-2026-62475](https://insights.sbomify.com/CVE-2026-62475/): Auth bypass in Oracle Shipping Execution (medium 6.6)
- [CVE-2016-5532](https://insights.sbomify.com/CVE-2016-5532/): Information disclosure in n/a (medium 5.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-60918 is a high-severity vulnerability in Oracle Shipping Execution, published on 21 Jul 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-60918 in the wild and no public exploit code.

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

## Sources

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

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