# CVE-2026-101532: Vulnerability in the Oracle EDI Gateway product of Oracle E-Business Suite (component: All Miscellaneous EDI Issues).


- **Severity:** High 7.2 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 20 Oct 2026
- **Updated:** 20 Oct 2026
- **Also known as:** GHSA-2wmc-3gfw-45wh

## What is CVE-2026-101532?

CVE-2026-101532 is a high-severity vulnerability in Oracle EDI Gateway, published on 20 Oct 2026. 

### Official description

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

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


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

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

## Is CVE-2026-101532 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-101532 is a high-severity vulnerability in Oracle EDI Gateway, published on 20 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-101532 in the wild and no public exploit code.

Affected product: Oracle EDI Gateway. 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-101532/ (Markdown: https://insights.sbomify.com/CVE-2026-101532/index.md)
```

## Sources

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

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