# CVE-2026-60579: Auth bypass in Oracle Enterprise Command Center Framework

> Unauthenticated attackers on the local network can bypass authentication to read, create, delete, or modify critical data in Oracle Enterprise Command Center Framework.

- **Severity:** High 8.0 (`CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:N`)
- **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-5564-p6x7-m79f

## What is CVE-2026-60579?

CVE-2026-60579 is a high-severity authentication bypass vulnerability in Oracle Enterprise Command Center Framework, 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 Enterprise Command Center Framework product of Oracle E-Business Suite (component: Core).   The supported version that is affected is V16. Difficult to exploit vulnerability allows unauthenticated attacker with access to the physical communication segment attached to the hardware where the Oracle Enterprise Command Center Framework executes to compromise Oracle Enterprise Command Center Framework.  While the vulnerability is in Oracle Enterprise Command Center Framework, 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 Enterprise Command Center Framework accessible data as well as  unauthorized access to critical data or complete access to all Oracle Enterprise Command Center Framework accessible data. CVSS 3.1 Base Score 8.0 (Confidentiality and Integrity impacts).  CVSS Vector: (CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:N).

Weakness: CWE-287 (Improper Authentication), CWE-284 (Improper Access Control)

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

It affects 1 product.


Products: Oracle Enterprise Command Center Framework.

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

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

## Is CVE-2026-60579 being exploited?

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

## Other vulnerabilities in Oracle Enterprise Command Center Framework

- [CVE-2026-46895](https://insights.sbomify.com/CVE-2026-46895/): Privilege escalation in Oracle Enterprise Command Center Framework (critical 9.9)
- [CVE-2026-46897](https://insights.sbomify.com/CVE-2026-46897/): Missing authorization in Oracle Enterprise Command Center Framework (critical 9.9)
- [CVE-2026-46900](https://insights.sbomify.com/CVE-2026-46900/): Privilege escalation in Oracle Enterprise Command Center Framework (critical 9.9)
- [CVE-2026-46901](https://insights.sbomify.com/CVE-2026-46901/): Privilege escalation in Oracle Enterprise Command Center Framework (critical 9.9)
- [CVE-2026-46902](https://insights.sbomify.com/CVE-2026-46902/): Auth bypass in Oracle Enterprise Command Center Framework (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-60579 is a high-severity authentication bypass vulnerability in Oracle Enterprise Command Center Framework, 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-60579 in the wild and no public exploit code.

Affected product: Oracle Enterprise Command Center Framework. 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-60579/ (Markdown: https://insights.sbomify.com/CVE-2026-60579/index.md)
```

## Sources

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

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