# CVE-2026-34296: Information disclosure in Oracle Agile Product Lifecycle Management for Process

> Low-privileged attackers can gain unauthorized read access to subset of data in Oracle Agile Product Lifecycle Management for Process via HTTP.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 21 Apr 2026
- **Updated:** 22 Apr 2026
- **Also known as:** GHSA-7mfh-vh4q-xgr5

## What is CVE-2026-34296?

CVE-2026-34296 is a medium-severity vulnerability in Oracle Agile Product Lifecycle Management for Process, published on 21 Apr 2026. Any signed-in user can exploit it over the 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: Product Quality Management).   The supported version that is affected is 6.2.4. Easily exploitable vulnerability allows low privileged attacker with network access via HTTP to compromise Oracle Agile Product Lifecycle Management for Process.  Successful attacks of this vulnerability can result in  unauthorized read access to a subset of Oracle Agile Product Lifecycle Management for Process accessible data. CVSS 3.1 Base Score 4.3 (Confidentiality impacts).  CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N).

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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

It affects 1 product.


Products: Oracle Agile Product Lifecycle Management for Process.

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

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

## Is CVE-2026-34296 being exploited?

There is no known exploitation of CVE-2026-34296 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-34296 and fix it if it is affected.

What it is: CVE-2026-34296 is a medium-severity vulnerability in Oracle Agile Product Lifecycle Management for Process, published on 21 Apr 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-34296 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-34296/ (Markdown: https://insights.sbomify.com/CVE-2026-34296/index.md)
```

## Sources

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

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