# CVE-2026-62519: Missing authorization in Oracle Succession planning

> Low-privileged attackers can modify, read, or disrupt Oracle Succession planning data via HTTP due to missing authorization checks.

- **Severity:** Medium 6.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L`)
- **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-g2w4-mjfp-3vj9

## What is CVE-2026-62519?

CVE-2026-62519 is a medium-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 Succession planning product of Oracle E-Business Suite (component: Succession plan).  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 Succession planning.  Successful attacks of this vulnerability can result in  unauthorized update, insert or delete access to some of Oracle Succession planning accessible data as well as  unauthorized read access to a subset of Oracle Succession planning accessible data and unauthorized ability to cause a partial denial of service (partial DOS) of Oracle Succession planning. CVSS 3.1 Base Score 6.3 (Confidentiality, Integrity and Availability impacts).  CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L).

Weakness: CWE-732 (Incorrect Permission Assignment for Critical Resource), CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor), CWE-284 (Improper Access Control), CWE-20 (Improper Input Validation)

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

It affects 1 product.


Products: Oracle E-Business Suite.

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

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

## Is CVE-2026-62519 being exploited?

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

What it is: CVE-2026-62519 is a medium-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-62519 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-62519/ (Markdown: https://insights.sbomify.com/CVE-2026-62519/index.md)
```

## Sources

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

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