Jd Edwards Enterpriseone ToolsApplication · Oracle

CVE-2026-46905

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: Web Runtime 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 HTTP 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

A critical unauthenticated remote code execution vulnerability in the Web Runtime Security component of JD Edwards EnterpriseOne Tools versions 9.2.0.0 through 9.2.26.2 allows attackers with network access via HTTP to completely compromise the system, achieving full takeover across confidentiality, integrity, and availability.

MitigationApply the Oracle security patch for CVE-2026-46905 immediately. If patches are unavailable, restrict network access to JD Edwards web interfaces via firewall rules or web application firewall until the official patch can be deployed.

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. Confirm JD Edwards EnterpriseOne Tools installation
    Locate the Oracle JD Edwards EnterpriseOne Tools installation directory or check system inventory for the presence of this Oracle product.
    Affected if The product is not installed on the system.
  2. Determine installed Tools version
    Access the JD Edwards EnterpriseOne Administration Console, check the installed packages via the Oracle JD Edwards Package Manager, or query the version through the EnterpriseOne deployment information. Compare the version number against the affected range 9.2.0.0 through 9.2.26.2.
    Affected if The installed version falls within 9.2.0.0 to 9.2.26.2.
  3. Verify Web Runtime Security component status
    Check the JD Edwards EnterpriseOne Server Manager or Web Runtime configuration to determine if the Web Runtime Security component is enabled and running.
    Affected if Web Runtime Security component is enabled and exposed.
  4. Check HTTP accessibility of web interfaces
    Identify all network-accessible URLs for JD Edwards web components (typically ports 8000-8003 or custom configured ports). Verify if these endpoints are reachable from untrusted networks.
    Affected if JD Edwards web interfaces are accessible via HTTP from the network.

A system is affected if JD Edwards EnterpriseOne Tools version 9.2.0.0 through 9.2.26.2 is installed with Web Runtime Security enabled and the HTTP web interface is network-accessible, allowing unauthenticated remote code execution.

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.

From vendor data
Upgrade available Upgrade to a release after 9.2.26.2
Interim mitigation

Apply the Oracle security patch for CVE-2026-46905 immediately. If patches are unavailable, restrict network access to JD Edwards web interfaces via firewall rules or web application firewall until the official patch can be deployed.

Fix this in Jd Edwards Enterpriseone Tools Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing12.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,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 $7,616.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

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