# CVE-2026-87313: Vulnerability in the JD Edwards EnterpriseOne Tools product of Oracle JD Edwards (component: Interoperability SEC).


- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 20 Oct 2026
- **Updated:** 28 Oct 2026
- **Also known as:** GHSA-qg3g-5hfg-x3mf

## What is CVE-2026-87313?

CVE-2026-87313 is a high-severity vulnerability in Oracle Corporation JD Edwards EnterpriseOne Tools, published on 20 Oct 2026. 

### Official description

Vulnerability in the JD Edwards EnterpriseOne Tools product of Oracle JD Edwards (component: Interoperability SEC).  Supported versions that are affected are 9.2.0.0-9.2.26.5. Easily exploitable vulnerability allows low privileged attacker with network access via JDENET to compromise JD Edwards EnterpriseOne Tools.  Successful attacks of this vulnerability can result in takeover of JD Edwards EnterpriseOne Tools. CVSS 3.1 Base Score 8.8 (Confidentiality, Integrity and Availability impacts).  CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H).

Weakness: CWE-306 (Missing Authentication for Critical Functionality)

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


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

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

## Is CVE-2026-87313 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-87313 is a high-severity vulnerability in Oracle Corporation JD Edwards EnterpriseOne Tools, published on 20 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-87313 in the wild and no public exploit code.

Affected product: Oracle Corporation JD Edwards EnterpriseOne Tools. 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-87313/ (Markdown: https://insights.sbomify.com/CVE-2026-87313/index.md)
```

## Sources

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

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