dbcve.org
Jd Edwards Enterpriseone ToolsApplication · Oracle

CVE-2026-46909

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

Unauthenticated remote code execution vulnerability in the Enterprise Infrastructure Security component of JD Edwards EnterpriseOne Tools allows attackers with network access via HTTP to completely take over the system without any credentials, achieving full confidentiality, integrity, and availability compromise.

MitigationApply Oracle's critical patch update for JD Edwards EnterpriseOne Tools versions 9.2.0.0-9.2.26.2 immediately. Until patched, restrict network exposure of HTTP interfaces and implement WAF rules as compensating controls.

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 JD Edwards EnterpriseOne Tools version
    Locate the installed JD Edwards EnterpriseOne Tools version via Oracle Enterprise Manager, or check the installation directory for version information, or run the Oracle version verification utility provided with the Tools installation.
    Affected if The installed version number falls within the range 9.2.0.0 through 9.2.26.2 inclusive.
  2. Confirm Enterprise Infrastructure Security component is present
    Verify that the Enterprise Infrastructure Security component is installed and enabled within the JD Edwards EnterpriseOne Tools environment. This may be visible in the Oracle Enterprise Manager console under Tools component listings, or via the JDE ORACLE HOME directory structure.
    Affected if The Enterprise Infrastructure Security component is present and enabled in the installation.
  3. Determine if HTTP interfaces are network-exposed
    Review network configuration and firewall rules to determine whether the JD Edwards EnterpriseOne HTTP listener ports (typically ports 80 or 8080 for the Web tier) are accessible from untrusted networks. Check if the web container serving the Tools application is bound to externally accessible network interfaces.
    Affected if HTTP interfaces for JD Edwards are exposed to network-accessible IP addresses outside the trusted internal network.
  4. Verify no authentication is required for the affected endpoint
    If Enterprise Infrastructure Security component is running, attempt to access the Enterprise Infrastructure Security functionality over HTTP without providing credentials. Review the component's configuration to confirm authentication is not enforced on the affected service endpoint.
    Affected if The Enterprise Infrastructure Security component accepts unauthenticated HTTP requests, allowing network attackers to reach the vulnerable endpoint without credentials.

You are affected if your JD Edwards EnterpriseOne Tools version is 9.2.0.0 through 9.2.26.2 AND the Enterprise Infrastructure Security component is enabled AND its HTTP interface is network-accessible without authentication.

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 critical patch update for JD Edwards EnterpriseOne Tools versions 9.2.0.0-9.2.26.2 immediately. Until patched, restrict network exposure of HTTP interfaces and implement WAF rules as compensating controls.

Recommended fix Moderate confidence

Oracle JD Edwards EnterpriseOne Tools version > 9.2.26.2 (specific fixed version available in Oracle Critical Patch Update advisory)

  1. 1. Identify the current JD Edwards EnterpriseOne Tools version installed in your environment using the Oracle JD Edwards EnterpriseOne Administrator or the Server Manager.
  2. 2. Review Oracle's official Critical Patch Update advisory for the corresponding quarter to confirm the exact fixed version for CVE-2026-46909.
  3. 3. Download the Oracle JD Edwards EnterpriseOne Tools patch for the fixed release (version > 9.2.26.2) from Oracle Support (support.oracle.com).
  4. 4. Apply the patch in a non-production environment first to validate compatibility with your existing JD Edwards configuration.
  5. 5. Schedule a maintenance window and apply the patch to production systems following Oracle's documented patch application procedures.
  6. 6. After patching, verify the JD Edwards EnterpriseOne Tools services restart successfully and the application functions normally.
  7. 7. Validate that the Enterprise Infrastructure Security component is no longer exposed to unauthenticated network access by reviewing access controls and network configurations.
Caveat Review Oracle's patch documentation for any required post-patch configuration changes or dependencies; test thoroughly in non-production before applying to production

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-46909 — 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-46909 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