# CVE-2026-71049: Missing authorization in Oracle Product Lifecycle Analytics

> Low-privileged attackers can access and modify critical data in Oracle Product Lifecycle Analytics via network access.

- **Severity:** High 8.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:L/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:** 18 Aug 2026
- **Updated:** 25 Aug 2026
- **Also known as:** GHSA-wfj2-5rr7-gf5f

## What is CVE-2026-71049?

CVE-2026-71049 is a high-severity missing authorization vulnerability in Oracle Product Lifecycle Analytics, published on 18 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Vulnerability in the Oracle Product Lifecycle Analytics product of Oracle Supply Chain (component: Installation Issues).   The supported version that is affected is 3.6.1. Easily exploitable vulnerability allows low privileged attacker with network access via Oracle Net to compromise Oracle Product Lifecycle Analytics.  While the vulnerability is in Oracle Product Lifecycle Analytics, 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 Product Lifecycle Analytics accessible data as well as  unauthorized update, insert or delete access to some of Oracle Product Lifecycle Analytics accessible data. CVSS 3.1 Base Score 8.5 (Confidentiality and Integrity impacts).  CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:L/A:N).

Weakness: CWE-284 (Improper Access Control)

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

It affects 1 product.


Products: Oracle Product Lifecycle Analytics.

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

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

## Is CVE-2026-71049 being exploited?

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

## Other vulnerabilities in Oracle Product Lifecycle Analytics

- [CVE-2026-61175](https://insights.sbomify.com/CVE-2026-61175/): Missing authorization in Oracle Product Lifecycle Analytics (critical 9.3)
- [CVE-2026-61174](https://insights.sbomify.com/CVE-2026-61174/): Missing authorization in Oracle Product Lifecycle Analytics (critical 9.0)
- [CVE-2026-71051](https://insights.sbomify.com/CVE-2026-71051/): Privilege escalation in Oracle Product Lifecycle Analytics (high 8.8)
- [CVE-2026-71050](https://insights.sbomify.com/CVE-2026-71050/): Missing authorization in Oracle Product Lifecycle Analytics (high 8.7)
- [CVE-2026-71048](https://insights.sbomify.com/CVE-2026-71048/): Missing authorization in Oracle Product Lifecycle Analytics (high 7.6)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-71049 is a high-severity missing authorization vulnerability in Oracle Product Lifecycle Analytics, published on 18 Aug 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-71049 in the wild and no public exploit code.

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

## Sources

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

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