# CVE-2026-46817: Oracle E-Business Suite Improper Privilege Management

> Unauthenticated attackers can compromise Oracle Payments via HTTP, leading to full system takeover and privilege escalation.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Yes, since 15 Jul 2026 (CISA KEV)
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 28 May 2026
- **Updated:** 16 Jul 2026
- **Also known as:** GHSA-pv4m-gf99-c5jr

## What is CVE-2026-46817?

CVE-2026-46817 is a critical authentication bypass vulnerability in Oracle E-Business Suite, published on 28 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Vulnerability in the Oracle Payments product of Oracle E-Business Suite (component: File Transmission).  Supported versions that are affected are 12.2.3-12.2.15. Easily exploitable vulnerability allows unauthenticated attacker with network access via HTTP to compromise Oracle Payments.  Successful attacks of this vulnerability can result in takeover of Oracle Payments. CVSS 3.1 Base Score 9.8 (Confidentiality, Integrity and Availability impacts).  CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H).

Weakness: CWE-287 (Improper Authentication), CWE-306 (Missing Authentication for Critical Functionality), CWE-269 (Improper Privilege Management)

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

It affects 1 product.


Products: Oracle E-Business Suite.

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

No fix has been published for CVE-2026-46817 yet. Limit exposure of the affected software until one is available. US federal agencies must fix it by 18 Jul 2026.

## Is CVE-2026-46817 being exploited?

Yes. Attackers have exploited CVE-2026-46817 in the wild since at least 15 Jul 2026.

Public exploit code:

- CVE-2026-46817 (github_poc): https://github.com/0xredash/CVE-2026-46817
- CVE-2026-46817 - Draft (github_poc): https://github.com/HORKimhab/CVE-2026-46817

## Other vulnerabilities in Oracle E-Business Suite

- [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)
- [CVE-2007-5528](https://insights.sbomify.com/CVE-2007-5528/): Other in n/a (critical 10.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-46817 is a critical authentication bypass vulnerability in Oracle E-Business Suite, published on 28 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: Yes. Attackers have exploited CVE-2026-46817 in the wild since at least 15 Jul 2026.

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-46817/ (Markdown: https://insights.sbomify.com/CVE-2026-46817/index.md)
```

## Sources

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

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