# CVE-2026-62513: Missing authorization in Oracle Process Manufacturing Regulatory Management

> Low-privileged attackers can bypass authorization to read critical data and modify some records in Oracle Process Manufacturing Regulatory Management.

- **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:** 21 Jul 2026
- **Updated:** 22 Jul 2026
- **Also known as:** GHSA-hw42-9jh7-m6w3

## What is CVE-2026-62513?

CVE-2026-62513 is a high-severity missing authorization vulnerability in Oracle E-Business Suite, published on 21 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Vulnerability in the Oracle Process Manufacturing Regulatory Management product of Oracle E-Business Suite (component: Internal Operations).  Supported versions that are affected are 12.2.3-12.2.15. Easily exploitable vulnerability allows low privileged attacker with network access via HTTP to compromise Oracle Process Manufacturing Regulatory Management.  While the vulnerability is in Oracle Process Manufacturing Regulatory Management, 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 Process Manufacturing Regulatory Management accessible data as well as  unauthorized update, insert or delete access to some of Oracle Process Manufacturing Regulatory Management 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-62513?

It affects 1 product.


Products: Oracle E-Business Suite.

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

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

## Is CVE-2026-62513 being exploited?

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

## Other vulnerabilities in Oracle E-Business Suite

- [CVE-2026-46817](https://insights.sbomify.com/CVE-2026-46817/): Oracle E-Business Suite Improper Privilege Management (critical 9.8, exploited in the wild)
- [CVE-2022-21587](https://insights.sbomify.com/CVE-2022-21587/): Oracle E-Business Suite Unspecified (critical 9.8, exploited in the wild)
- [CVE-2015-4798](https://insights.sbomify.com/CVE-2015-4798/): Other in n/a (critical 10.0)
- [CVE-2015-4839](https://insights.sbomify.com/CVE-2015-4839/): Other in n/a (critical 10.0)
- [CVE-2008-1826](https://insights.sbomify.com/CVE-2008-1826/): Other in n/a (critical 10.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-62513 is a high-severity missing authorization vulnerability in Oracle E-Business Suite, published on 21 Jul 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-62513 in the wild and no public exploit code.

Affected product: Oracle E-Business Suite. 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-62513/ (Markdown: https://insights.sbomify.com/CVE-2026-62513/index.md)
```

## Sources

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

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