dbcve.org
Jd Edwards Enterpriseone ToolsApplication · Oracle

CVE-2026-46904

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 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.

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 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.

dbcve analysis · high confidence

Critical vulnerability in Oracle JD Edwards EnterpriseOne Tools (Enterprise Infrastructure Security component) affecting versions 9.2.0.0-9.2.26.2. Easily exploitable via JDENET protocol by unauthenticated attackers with network access, allowing complete system takeover with full confidentiality, integrity, and availability impact.

MitigationApply Oracle's security patch for CVE-2026-46904 immediately. Until patched, restrict network access to JDENET ports and implement additional monitoring on affected systems.

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

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.

NVD · CPE data
Jd Edwards Enterpriseone ToolsApplication
Affected:>= 9.2.0.0, <= 9.2.26.2

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.

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? 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.

dbcve checks

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

  1. Identify if JD Edwards EnterpriseOne Tools is installed
    Check system for Oracle JD Edwards EnterpriseOne Tools installation directories or installed software listings. Common locations include Oracle installation paths or enterprise application directories.
    Affected if The software is present on the system
  2. Determine the installed version of JD Edwards EnterpriseOne Tools
    Use Oracle administrative tools, version inspection commands, or check product-specific configuration files that contain the Tools version number.
    Affected if The installed version falls within 9.2.0.0 through 9.2.26.2
  3. Verify JDENET protocol is enabled
    Check JD Edwards configuration files and server settings for JDENET service availability. JDENET typically runs as a listener service for inter-component communication.
    Affected if JDENET is active and listening for connections
  4. Assess network exposure of JDENET services
    Review firewall rules, network segmentation, and port configurations to determine if JDENET ports are accessible from untrusted network segments. JDENET commonly uses specific TCP ports for communication.
    Affected if JDENET ports are exposed to network segments accessible by unauthenticated attackers

The environment is affected if JD Edwards EnterpriseOne Tools version 9.2.0.0-9.2.26.2 is installed with JDENET protocol enabled and accessible to unauthenticated network attackers.

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

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Upgrade available Upgrade to a release after 9.2.26.2
Interim mitigation

Apply Oracle's security patch for CVE-2026-46904 immediately. Until patched, restrict network access to JDENET ports and implement additional monitoring on affected systems.

Recommended fix Moderate confidence

9.2.27.x or later (or latest patch from Oracle Critical Patch Update)

  1. 1. Review the Oracle Critical Patch Update advisory for the security fix addressing CVE-2026-46904.
  2. 2. Identify the recommended fixed version or patch number for JD Edwards EnterpriseOne Tools from the Oracle advisory.
  3. 3. Download the corresponding patch or upgraded version from Oracle's support website (My Oracle Support).
  4. 4. Test the patch/upgrade in a non-production environment to verify compatibility with existing configurations.
  5. 5. Apply the patch or perform the upgrade during a scheduled maintenance window.
  6. 6. Verify the fix is applied by checking the JD Edwards EnterpriseOne Tools version number.
Caveat Review Oracle's upgrade documentation for JD Edwards EnterpriseOne Tools 9.2.27 for any configuration or compatibility changes

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

Fix this in Jd Edwards Enterpriseone Tools Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA8.0 h
44.0 hours of engineering $7,720
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-46904 — 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 Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

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

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