dbcve.org
Jd Edwards Enterpriseone ToolsApplication · Oracle

CVE-2026-60627

CRITICAL · 9.9 CVSS v3.1 Published 2026-07-21
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable Zero-click 4 weeks old

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: Installation Security). The supported version that is affected is 9.2.26.3. Easily exploitable vulnerability allows low privileged attacker with network access via HTTP to compromise JD Edwards EnterpriseOne Tools. While the vulnerability is in JD Edwards EnterpriseOne Tools, attacks may significantly impact additional products (scope change). Successful attacks of this vulnerability can result in takeover of JD Edwards EnterpriseOne Tools. CVSS 3.1 Base Score 9.9 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/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 · moderate confidence

A critical vulnerability in the Installation Security component of JD Edwards EnterpriseOne Tools version 9.2.26.3 allows low-privileged attackers with network access via HTTP to compromise the system and potentially take it over. The CVSS scope change indicates attacks may also impact additional products in the enterprise environment.

MitigationApply Oracle's security patch for JD Edwards EnterpriseOne Tools 9.2.26.3 or upgrade to a patched version. Until patched, restrict network access to HTTP interfaces and enforce additional authentication 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.26.3

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
Low
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/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 installation
    Locate the JD Edwards EnterpriseOne Tools installation directory or check system inventory/scm for Oracle JD Edwards components. Common locations include $JDE_HOME/system or similar. Query the installed packages or Oracle inventory if available.
    Affected if JD Edwards EnterpriseOne Tools is not installed on the system
  2. Determine installed Tools version
    Check the version of JD Edwards EnterpriseOne Tools installed. This is typically found in the installation manifest, Oracle inventory, or by querying the system via Oracle system tables or deployment metadata. Look for a version string matching 9.2.26.3.
    Affected if The installed version is exactly 9.2.26.3
  3. Verify Installation Security component is present
    Check if the Installation Security component is deployed within the JD Edwards EnterpriseOne Tools installation. This may be visible in the component list, deployment configuration, or as a named module within the Tools suite.
    Affected if Installation Security component exists in the deployment
  4. Confirm HTTP interface is enabled for Installation Security
    Inspect the configuration for the Installation Security component to determine if HTTP access is enabled. This is typically configured in the web server or application server settings (Oracle WebLogic, IBM WebSphere) binding the Installation Security port.
    Affected if HTTP interface for Installation Security is exposed and accessible
  5. Check network accessibility of the HTTP port
    Determine if the HTTP port used by Installation Security (commonly ports in the 8000-9000 range) is reachable from untrusted networks. Review firewall rules, load balancer settings, and network segment restrictions.
    Affected if The HTTP port is accessible from untrusted network segments or the public internet

You are affected if JD Edwards EnterpriseOne Tools version 9.2.26.3 is installed with the Installation Security component accessible via HTTP from your network.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply Oracle's security patch for JD Edwards EnterpriseOne Tools 9.2.26.3 or upgrade to a patched version. Until patched, restrict network access to HTTP interfaces and enforce additional authentication controls.

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

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