# CVE-2026-114890: Other in Oracle Trade Management

> Low-privileged remote attackers can access all Oracle Trade Management data via HTTP.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Harmful if only installed:** No
- **Needs a specific call:** No
- **Fix available:** No
- **Published:** 17 Nov 2026
- **Updated:** 19 Nov 2026
- **Also known as:** GHSA-9f28-3gfx-gq3x

## What is CVE-2026-114890?

CVE-2026-114890 is a medium-severity other vulnerability in Oracle Trade Management, published on 17 Nov 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Vulnerability in the Oracle Trade Management product of Oracle E-Business Suite (component: Claim LOV).  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 Trade Management.  Successful attacks of this vulnerability can result in  unauthorized access to critical data or complete access to all Oracle Trade Management accessible data. CVSS 3.1 Base Score 6.5 (Confidentiality impacts).  CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N).

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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

An affected version is exposed as installed. No special setting or call is needed.


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

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

## Is CVE-2026-114890 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-114890 is a medium-severity other vulnerability in Oracle Trade Management, published on 17 Nov 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-114890 in the wild and no public exploit code.
Exposure: An affected version is exposed as installed. No special setting or call is needed.

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

## Sources

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

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