Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessIdentify exposed Orchestrator HTTP endpoint
-
ExploitSend crafted unauthenticated request
-
ExecutionBypass access control on E1 IOT component
-
ImpactRetrieve subset of accessible data
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V14 - Data Protection Data exposure prevention
MITRE ATT&CK
2 techniques across 2 tactics: Collection, Discovery The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Requires network access over HTTP to a running JD Edwards EnterpriseOne Orchestrator instance exposing the E1 IOT Orchestrator Security component; affected supported versions are 9.2.0.0 through 9.2.26.5. No authentication, no privileges, and no user interaction are required (PR:N/UI:N), so any network-reachable instance in that version range is exploitable in its as-deployed state. The main limiting factor is reachability: Orchestrator is typically an internal/integration-tier service, so risk is dominated by whether the endpoint is exposed to untrusted networks or the internet rather than by any special configuration. Impact is further bounded to read access to only a subset of Orchestrator data (C:L, I:N, A:N). |
| Impact | This is a moderate-severity information-disclosure flaw (CVSS 3.1 base 5.3, vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N) carrying confidentiality-only impact with no integrity or availability effect. The CVSS vector is favorable to attackers on exposure metrics - network attack vector, low complexity, no privileges, and no user interaction - meaning any reachable instance can be probed by an unauthenticated remote attacker. However, the actual damage is capped: Oracle describes only 'unauthorized read access to a subset' of Orchestrator data, which is why the score lands at 5.3 (medium) rather than critical despite the easy exploitability. No EPSS score, CISA KEV listing, or public proof-of-concept was provided in the input, so there is no public exploit identified at time of analysis and no evidence of active exploitation. The practical takeaway: this is an easily-triggerable but low-impact issue - a genuine patch-in-the-next-cycle item for internet-exposed Orchestrator instances rather than an emergency. One signal conflict to note: the input Tags include 'Authentication Bypass', but Oracle's description characterizes the issue as unauthorized partial read access, not a full authentication bypass; treat the tag as loosely applied and rely on the CVSS confidentiality-only profile. |
| Exploit ScenarioDerived | An unauthenticated attacker with network reachability to an internet-exposed or internal JD Edwards EnterpriseOne Orchestrator endpoint sends a crafted HTTP request to the E1 IOT Orchestrator Security component. Because no authentication or user interaction is required (PR:N/UI:N), the request returns a subset of Orchestrator-accessible data the attacker should not be able to read. No public exploit code was identified in the provided intelligence, so this reflects the vector's theoretical ease rather than a confirmed in-the-wild technique. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 21, 2026
Unauthenticated information disclosure in Oracle JD Edwards EnterpriseOne Orchestrator (supported releases 9.2.0.0 through 9.2.26.5) lets any party able to reach the Orchestrator over HTTP read a subset of Orchestrator-accessible data without credentials, privileges, or user interaction (CVSS 3.1 base 5.3, CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N). The flaw sits in the E1 IOT Orchestrator Security component and is best characterized as an access-control/authentication bypass that yields confidentiality-only impact - no integrity or availability effect - so the practical exposure is bounded to whatever data the reachable endpoint returns. Exploitation requires only network reachability, making risk dominated by whether the Orchestrator tier is internet-exposed or reachable from untrusted segments; no public exploit code has been identified at time of analysis and there is no CISA KEV confirmation of active exploitation. Oracle addresses the issue in its October 2026 Critical Patch Update.
RemediationAI
Apply the Oracle Critical Patch Update for October 2026 (https://www.oracle.com/security-alerts/cpuoct2026.html), which is the vendor-released fix for CVE-2026-91277 - patch status is 'Patch available per vendor advisory'; no specific minimum fixed version number is confirmed in the supplied data, so verify the fixed Orchestrator release against Oracle's CPU version matrix before closing the finding. Until patching is complete, the highest-value control is reducing reachability: restrict HTTP access to the Orchestrator endpoints to known integration hosts via network ACLs or security groups and remove any internet or DMZ exposure, accepting that this breaks legitimate external integrations that must then be re-homed behind a broker. Front the Orchestrator with an authenticating reverse proxy or WAF and require client credentials at that layer, with the trade-off of added latency and a second authentication configuration to maintain; disable or undeploy unused orchestrations and versions to shrink the reachable endpoint surface, at the cost of re-enabling work if a retired orchestration is still needed; and monitor Orchestrator/HTTP access logs for unauthenticated requests returning data, noting that detection is limited because the traffic is otherwise well-formed and low-volume.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
Oracle JD Edwards EnterpriseOne Orchestrator is the low-code integration/orchestration tier of EnterpriseOne: it exposes HTTP/REST-style endpoints through which internal systems invoke orchestrations, business functions, and AIS-style services without direct JDE client connectivity. The affected component, E1 IOT Orchestrator Security, is the layer that is supposed to enforce caller authentication and authorization on those requests. The supplied vector (PR:N/UI:N with C:L, I:N, A:N) and the 'Authentication Bypass' tag indicate that a security check on an Orchestrator-accessible path can be circumvented, letting an unauthenticated HTTP client retrieve a limited subset of Orchestrator data rather than taking over the application. No CWE was assigned by the source, but the behavior aligns with missing or improperly enforced authorization on a network-reachable endpoint (CWE-306/CWE-862 class). Because the attack is AC:L and requires no privileges or interaction, the only real gate is network reachability of the Orchestrator service, which is normally deployed as an internal integration-tier component behind the corporate perimeter rather than as an internet-facing application.
Know when the next one hits your stack
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
Unauthenticated remote HTTP exploitation gives AV:N/AC:L/PR:N/UI:N; impact is limited unauthorized read of a data subset, so C:L with I:N/A:N and unchanged scope.
Primary rating from Vendor (oracle).
CVSS VectorVendor: oracle
DescriptionCVE.org
Vulnerability in the JD Edwards EnterpriseOne Orchestrator product of Oracle JD Edwards (component: E1 IOT Orchestrator Security). Supported versions that are affected are 9.2.0.0-9.2.26.5. Easily exploitable vulnerability allows unauthenticated attacker with network access via HTTP to compromise JD Edwards EnterpriseOne Orchestrator. Successful attacks of this vulnerability can result in unauthorized read access to a subset of JD Edwards EnterpriseOne Orchestrator accessible data. CVSS 3.1 Base Score 5.3 (Confidentiality impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N).
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.
EUVD-2026-106531
GHSA-rc46-f8x5-6p3x
NVD
CVE.org
EPSS
Exploit-DB