Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB
CVE-2026-91285 Overview
CVE-2026-91285 affects Oracle JD Edwards EnterpriseOne Orchestrator, specifically the E1 IOT Orchestrator Security component. The flaw impacts supported versions 9.2.0.0 through 9.2.26.5. A low-privileged attacker with network access over HTTP can exploit this weakness to compromise confidentiality of data processed by the Orchestrator.
Oracle disclosed the issue in the October 2026 Critical Patch Update. The vulnerability does not affect integrity or availability, but successful exploitation grants unauthorized access to all data reachable through the Orchestrator service.
Critical Impact
An authenticated attacker over the network can read all data accessible to the JD Edwards EnterpriseOne Orchestrator, including sensitive business records exposed through orchestration workflows.
Affected Products
- Oracle JD Edwards EnterpriseOne Orchestrator 9.2.0.0 through 9.2.26.5
- E1 IOT Orchestrator Security component
- Deployments exposing the Orchestrator HTTP interface to internal or external networks
Discovery Timeline
- 2026-10-20 - CVE-2026-91285 published to NVD
- 2026-10-21 - Last updated in NVD database
- October 2026 - Addressed in Oracle Critical Patch Update (Oracle Security Alert - October 2026)
Technical Details for CVE-2026-91285
Vulnerability Analysis
The weakness resides in the E1 IOT Orchestrator Security component of JD Edwards EnterpriseOne Orchestrator. The Orchestrator exposes HTTP endpoints that invoke orchestrations, service requests, and notifications against business data. A low-privileged authenticated user can abuse these interfaces to retrieve data beyond their intended authorization scope.
Because the attack vector is network-based with low complexity, exploitation does not require user interaction. The impact is bounded to confidentiality, meaning data cannot be altered or destroyed through this flaw, but any records reachable by the Orchestrator process can be read.
The EPSS probability stands at 0.355% with a percentile of 28.031, reflecting a currently low observed exploitation likelihood. No public proof-of-concept or active exploitation has been reported at the time of publication.
Root Cause
Oracle has not released detailed technical specifics beyond the advisory. The flaw is categorized under broken access control in the Orchestrator Security component, allowing privilege boundaries to be crossed when authenticated requests target data-returning orchestrations.
Attack Vector
Exploitation requires network reachability to the Orchestrator HTTP endpoint and valid low-privilege credentials for a JD Edwards EnterpriseOne account. The attacker crafts HTTP requests against orchestration endpoints that return business data the account should not otherwise access. Refer to the Oracle Security Alert - October 2026 for authoritative details.
Detection Methods for CVE-2026-91285
Indicators of Compromise
- Unusual volume of HTTP requests to /jderest/orchestrator, /jderest/v2/orchestrator, or related Orchestrator endpoints from a single authenticated user
- Orchestration invocations from accounts that do not normally interact with the Orchestrator API
- Repeated requests enumerating orchestration names, service requests, or notification endpoints
Detection Strategies
- Baseline Orchestrator API usage per user and alert on deviations in request rate, orchestration diversity, or response size
- Correlate authentication events for low-privileged JD Edwards accounts with Orchestrator REST API calls returning large result sets
- Review AIS Server and Orchestrator Studio audit logs for orchestrations executed outside documented business workflows
Monitoring Recommendations
- Forward JD Edwards EnterpriseOne Orchestrator and AIS Server logs to a centralized log platform for retention and query
- Enable HTTP access logging on the Orchestrator reverse proxy or load balancer and retain for incident response
- Monitor outbound data transfer volumes from the Orchestrator host to identify bulk data exfiltration
How to Mitigate CVE-2026-91285
Immediate Actions Required
- Apply the Oracle October 2026 Critical Patch Update to all JD Edwards EnterpriseOne Orchestrator instances running versions 9.2.0.0 through 9.2.26.5
- Inventory all Orchestrator deployments, including non-production environments, and prioritize internet-exposed systems
- Audit low-privileged accounts with Orchestrator access and remove unnecessary entitlements
Patch Information
Oracle addressed CVE-2026-91285 in the October 2026 Critical Patch Update. Review the Oracle Security Alert - October 2026 for the specific patch bundle and installation instructions covering JD Edwards EnterpriseOne Orchestrator.
Workarounds
- Restrict network access to the Orchestrator HTTP endpoint using firewall rules, allowing only trusted application tiers and administrative hosts
- Enforce least-privilege role assignments for JD Edwards EnterpriseOne users who can invoke orchestrations
- Disable or remove unused orchestrations, service requests, and notifications to reduce the exposed attack surface
# Example: restrict Orchestrator endpoint to internal application tier
# (adjust interface, source range, and port to match your deployment)
iptables -A INPUT -p tcp --dport 9090 -s 10.10.0.0/16 -j ACCEPT
iptables -A INPUT -p tcp --dport 9090 -j DROP
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB

