Jd Edwards Enterpriseone ToolsApplication · Oracle

CVE-2026-46880

CRITICAL · 9.8 CVSS v3.1 Published 2026-06-17

Fix available

A fix is available. Upgrade to after 9.2.26.2 or later.

See remediation →

100/100

Remediation priority · Urgent

Remotely reachable No privileges Zero-click

Official description

NVD · unedited

Vulnerability in the JD Edwards EnterpriseOne Tools product of Oracle JD Edwards (component: Enterprise Infrastructure Security). Supported versions that are affected are 9.2.0.0-9.2.26.2. Easily exploitable vulnerability allows unauthenticated 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 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).

Technical summary

dbcve analysis · high confidence

Unauthenticated remote code execution vulnerability in the Enterprise Infrastructure Security component of JD Edwards EnterpriseOne Tools (versions 9.2.0.0-9.2.26.2). Attackers can exploit this via the JDENET network protocol to achieve full system compromise including confidentiality, integrity, and availability impacts.

MitigationApply Oracle's security patch for this vulnerability immediately. As an interim measure, restrict network access to JDENET ports from untrusted sources until patching can be completed.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions

NVD · CPE data

Jd Edwards Enterpriseone ToolsApplication

Affected:>= 9.2.0.0, <= 9.2.26.2

CVSS breakdown

From the vector

Attack vector: Network
Complexity: Low
Privileges: None
User interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: High
Availability: High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected?

dbcve checks

Work through these to decide whether this CVE applies to you.

Identify if JD Edwards EnterpriseOne Tools is installed

Look for JD Edwards EnterpriseOne Tools installation directories, or check system services for JDENET or EnterpriseOne-related services. On Windows, check Program Files for Oracle\JD Edwards\EnterpriseOne or similar paths. On UNIX/Linux, check /opt/oracle/ or similar Oracle installation paths.

Affected if JD Edwards EnterpriseOne Tools is installed on the system
Determine the installed version of JD Edwards EnterpriseOne Tools

Check the version of the installed EnterpriseOne Tools component. This is typically available in the installation directory, in version manifest files, or via the JDENET service information. Common locations include the Tools\bin folder or version.txt files within the Oracle\JD Edwards\EnterpriseOne directory structure.

Affected if The installed version falls within the range 9.2.0.0 to 9.2.26.2 inclusive
Verify the JDENET service is running and exposed

Check if the JDENET network service is active and listening on network ports. JDENET typically uses configurable ports (often in the 6000-9000 range). Use netstat or similar tools to identify listening ports associated with JDENET or EnterpriseOne processes.

Affected if The JDENET service is running and listening on network ports accessible from the network
Assess network exposure of the JDENET service

Review firewall rules and network ACLs to determine if the JDENET ports are accessible from untrusted network segments. Check if the service is bound to 0.0.0.0 or external interfaces rather than localhost only.

Affected if The JDENET service is accessible from untrusted network sources or the internet

A system is affected if JD Edwards EnterpriseOne Tools version 9.2.0.0 through 9.2.26.2 is installed with the JDENET service running and network-accessible from untrusted sources.

Generated from the published advisory. Verify against your own configuration.

Remediation

dbcve · scoped

Upgrade available Upgrade to a release after 9.2.26.2

Interim mitigation

Apply Oracle's security patch for this vulnerability immediately. As an interim measure, restrict network access to JDENET ports from untrusted sources until patching can be completed.

Recommended fix Moderate confidence

Upgrade to JD Edwards EnterpriseOne Tools version 9.2.27.0 or later (latest available stable release beyond 9.2.26.2)

1. Identify the current JD Edwards EnterpriseOne Tools version in your environment using the Oracle JD Edwards EnterpriseOne Administrator application or command line tools.
2. Review the Oracle JD Edwards EnterpriseOne Tools release notes for versions higher than 9.2.26.2 to identify the security fix for this vulnerability.
3. Download the latest JD Edwards EnterpriseOne Tools release from Oracle's official support portal (My Oracle Support).
4. Create a full backup of the current JD Edwards EnterpriseOne Tools environment, including the database, Middleware, and web tier components.
5. Test the upgrade in a non-production environment that mirrors production configuration before deploying.
6. Apply the upgrade following Oracle's official installation and upgrade documentation for JD Edwards EnterpriseOne Tools.
7. Verify the new version is running correctly and validate that the Enterprise Infrastructure Security component is functioning properly.
8. After successful production deployment, monitor system logs and Oracle support communications for any post-upgrade issues.

Caveat Review Oracle's release notes for any configuration, compatibility, or deprecation notices between 9.2.26.2 and the target version; some customizations or integrations may require updates.

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Jd Edwards Enterpriseone Tools Scoped from the published advisory

Consultation6.0 h
Implementation12.0 h
Testing10.0 h
Review / QA5.0 h

33.0 hours of engineering $5,760

Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $9,216.

Scan for this in your stack

Free · runs locally

dbcve dependency scanner

Check whether your project pulls in CVE-2026-46880 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References

Primary sources

www.oracle.comVendor Advisory
nvd.nist.govNVD record

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-46880 in production — separate from our analysis above.

Notes0 Guidelines

Know something about CVE-2026-46880?

The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.

The version that genuinely resolved it — not the one the vendor claimed
A config change or rule that shut the vector down
A gotcha in the upgrade path that cost you an afternoon

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here

Verified mitigations, workarounds, and config changes
Version or environment caveats, and links to real fixes
No weaponised exploit code, or anything meant to cause harm
No spam, self-promotion, credentials, or personal data

At a glance

A fix existsUpgrade to after 9.2.26.2 or later

Severity 9.8 Critical

Exploit likelihood EPSS, next 30 days 0.5%

Affects: Jd Edwards Enterpriseone Tools

Remediation

A high-priority fix

Fix this in Jd Edwards Enterpriseone Tools 33 hrs · High

Typical engagement from $5,760

Get a fix See the full breakdown ↓

A high-priority vulnerability. Send your environment and a specialist will scope CVE-2026-46880 and return a fixed quote and timeline.

You’ll deal with our team directly and deploy the reviewed fix to staging first — never straight to production.

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

Check your environment

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

Scan for this in your stack

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Practitioner notes

No notes yet

Official description

Technical summary

Affected products & versions

CVSS breakdown

Am I affected?

Remediation

References