dbcve.org
Jd Edwards Enterpriseone Global Order PromisingApplication · Oracle

CVE-2026-46907

CRITICAL · 9.9 CVSS v3.1 Published 2026-06-17
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

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 Order Promising product of Oracle JD Edwards (component: Order Promising Integration). The supported version that is affected is 9.2. Easily exploitable vulnerability allows low privileged attacker with network access via HTTP to compromise JD Edwards EnterpriseOne Order Promising. While the vulnerability is in JD Edwards EnterpriseOne Order Promising, attacks may significantly impact additional products (scope change). Successful attacks of this vulnerability can result in takeover of JD Edwards EnterpriseOne Order Promising. 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 network-exploitable vulnerability in JD Edwards EnterpriseOne Order Promising (component: Order Promising Integration) version 9.2 allows a low-privileged attacker with HTTP network access to achieve complete takeover of the affected component. The CVSS 9.9 score indicates trivial exploitability (low complexity, no user interaction, low privileges required) resulting in full confidentiality, integrity, and availability compromise, with scope change allowing impact to additional products.

MitigationApply the Oracle Critical Patch Update addressing CVE-2026-46907 for JD Edwards EnterpriseOne version 9.2 immediately. Until patched, restrict network access to Order Promising Integration endpoints to minimize attack surface.

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 Global Order PromisingApplication
Affected:= 9.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
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. Verify JD Edwards EnterpriseOne installation exists
    Locate JD Edwards EnterpriseOne installation directories or services on the system. Check common installation paths or use system inventory tools to identify Oracle JD Edwards software.
    Affected if JD Edwards EnterpriseOne software is found on the system
  2. Confirm installed version is 9.2
    Query the installed version of JD Edwards EnterpriseOne Global Order Promising using Oracle version utilities, configuration files, or installer records. Compare the detected version against the affected range (version 9.2).
    Affected if The installed version is exactly 9.2
  3. Determine if Order Promising Integration component is enabled
    Check the JD Edwards EnterpriseOne configuration to see if the Order Promising (formerly Global Order Promising) module or integration component is enabled and loaded.
    Affected if Order Promising Integration component is enabled and running
  4. Inspect HTTP listener exposure for Order Promising
    Review network listener configurations, web server settings, or JDE enterprise server configurations to identify if HTTP ports/services for Order Promising are active and bound to network interfaces.
    Affected if Order Promising HTTP interface is listening on network-accessible ports
  5. Assess network access to Order Promising HTTP service
    Check firewall rules, web server access controls, or network segmentation surrounding the Order Promising HTTP endpoints to determine if low-privileged network attackers can reach these interfaces.
    Affected if HTTP service for Order Promising is exposed to untrusted network access

The environment is affected if JD Edwards EnterpriseOne Global Order Promising version 9.2 is installed with the Order Promising Integration component enabled and its HTTP interface exposed to network access.

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 the Oracle Critical Patch Update addressing CVE-2026-46907 for JD Edwards EnterpriseOne version 9.2 immediately. Until patched, restrict network access to Order Promising Integration endpoints to minimize attack surface.

Fix this in Jd Edwards Enterpriseone Global Order Promising Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing12.0 h
  • Review / QA6.0 h
30.0 hours of engineering $5,120
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-46907 — 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-46907 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