# CVE-2026-61138: Missing authorization in Oracle Complex Maintenance, Repair and Overhaul

> Unauthenticated attackers can access and modify critical data in Oracle Complex Maintenance, Repair and Overhaul via HTTP.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 21 Jul 2026
- **Updated:** 23 Jul 2026
- **Also known as:** GHSA-m4f7-5v6r-8c8c

## What is CVE-2026-61138?

CVE-2026-61138 is a high-severity missing authorization vulnerability in Oracle Complex Maintenance, Repair and Overhaul, published on 21 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Vulnerability in the Oracle Complex Maintenance, Repair and Overhaul product of Oracle E-Business Suite (component: Internal Operations).  Supported versions that are affected are 12.2.3-12.2.15. Difficult to exploit vulnerability allows unauthenticated attacker with network access via HTTP to compromise Oracle Complex Maintenance, Repair and Overhaul.  While the vulnerability is in Oracle Complex Maintenance, Repair and Overhaul, attacks may significantly impact additional products (scope change).  Successful attacks of this vulnerability can result in  unauthorized access to critical data or complete access to all Oracle Complex Maintenance, Repair and Overhaul accessible data as well as  unauthorized update, insert or delete access to some of Oracle Complex Maintenance, Repair and Overhaul accessible data. CVSS 3.1 Base Score 7.5 (Confidentiality and Integrity impacts).  CVSS Vector: (CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:L/A:N).

Weakness: CWE-284 (Improper Access Control)

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

It affects 1 product.


Products: Oracle Complex Maintenance Repair and Overhaul.

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

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

## Is CVE-2026-61138 being exploited?

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

## Other vulnerabilities in Oracle Complex Maintenance, Repair and Overhaul

- [CVE-2026-46915](https://insights.sbomify.com/CVE-2026-46915/): Auth bypass in Oracle Complex Maintenance, Repair and Overhaul (high 8.5)
- [CVE-2016-3456](https://insights.sbomify.com/CVE-2016-3456/): Information disclosure in n/a (high 8.2)
- [CVE-2026-46934](https://insights.sbomify.com/CVE-2026-46934/): Auth bypass in Oracle Complex Maintenance, Repair and Overhaul (high 7.5)
- [CVE-2026-46935](https://insights.sbomify.com/CVE-2026-46935/): Auth bypass in Oracle Complex Maintenance, Repair and Overhaul (high 7.5)
- [CVE-2026-70820](https://insights.sbomify.com/CVE-2026-70820/): Auth bypass in Oracle Call Center Technology (high 7.2)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-61138 is a high-severity missing authorization vulnerability in Oracle Complex Maintenance, Repair and Overhaul, published on 21 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-61138 in the wild and no public exploit code.

Affected product: Oracle Complex Maintenance, Repair and Overhaul. 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-61138/ (Markdown: https://insights.sbomify.com/CVE-2026-61138/index.md)
```

## Sources

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

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