# CVE-2026-61182: Privilege escalation in Oracle Agile Product Lifecycle Management for Process

> A high-privileged attacker with local access can escalate privileges to fully compromise the Oracle Agile Product Lifecycle Management for Process system.

- **Severity:** Medium 6.7 (`CVSS:3.1/AV:L/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:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 21 Jul 2026
- **Updated:** 1 Aug 2026
- **Also known as:** GHSA-m29v-xp23-r35r

## What is CVE-2026-61182?

CVE-2026-61182 is a medium-severity vulnerability in Oracle Agile Product Lifecycle Management for Process, 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 Agile Product Lifecycle Management for Process product of Oracle Supply Chain (component: Data Import).   The supported version that is affected is 6.2.4. Easily exploitable vulnerability allows high privileged attacker with logon to the infrastructure where Oracle Agile Product Lifecycle Management for Process executes to compromise Oracle Agile Product Lifecycle Management for Process.  Successful attacks of this vulnerability can result in takeover of Oracle Agile Product Lifecycle Management for Process. CVSS 3.1 Base Score 6.7 (Confidentiality, Integrity and Availability impacts).  CVSS Vector: (CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H).

Weakness: CWE-269 (Improper Privilege Management)

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

It affects 1 product.


Products: Oracle Agile Product Lifecycle Management for Process.

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

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

## Is CVE-2026-61182 being exploited?

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

## Other vulnerabilities in Oracle Agile Product Lifecycle Management for Process

- [CVE-2026-61178](https://insights.sbomify.com/CVE-2026-61178/): Auth bypass in Oracle Agile Product Lifecycle Management for Process (critical 9.8)
- [CVE-2026-61183](https://insights.sbomify.com/CVE-2026-61183/): Auth bypass in Oracle Agile Product Lifecycle Management for Process (critical 9.8)
- [CVE-2026-21969](https://insights.sbomify.com/CVE-2026-21969/): Auth bypass in Oracle Agile Product Lifecycle Management for Process (critical 9.8)
- [CVE-2026-61184](https://insights.sbomify.com/CVE-2026-61184/): Missing authorization in Oracle Agile Product Lifecycle Management for Process (critical 9.1)
- [CVE-2026-61179](https://insights.sbomify.com/CVE-2026-61179/): Auth bypass in Oracle Agile Product Lifecycle Management for Process (high 8.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-61182 is a medium-severity vulnerability in Oracle Agile Product Lifecycle Management for Process, 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-61182 in the wild and no public exploit code.

Affected product: Oracle Agile Product Lifecycle Management for Process. 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-61182/ (Markdown: https://insights.sbomify.com/CVE-2026-61182/index.md)
```

## Sources

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

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