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-91305 Overview
CVE-2026-91305 is an authentication weakness [CWE-287] affecting the Installation Security component of Oracle JD Edwards EnterpriseOne Tools. The flaw impacts supported versions 9.2.0.0 through 9.2.26.5. An unauthenticated attacker with network access over HTTPS can compromise the product without user interaction. Successful exploitation grants read access to all JD Edwards EnterpriseOne Tools accessible data and allows unauthorized creation, deletion, or modification of that data. Oracle disclosed the issue in the October 2026 Critical Patch Update.
Critical Impact
Unauthenticated network attackers can read and modify all data accessible to JD Edwards EnterpriseOne Tools, placing confidentiality and integrity of ERP data at risk.
Affected Products
- Oracle JD Edwards EnterpriseOne Tools 9.2.0.0 through 9.2.26.5
- Installation Security component of JD Edwards EnterpriseOne Tools
- Deployments exposing the affected HTTPS interface to untrusted networks
Discovery Timeline
- 2026-10-20 - CVE-2026-91305 published to the National Vulnerability Database
- 2026-10-21 - Entry last modified in NVD
- October 2026 - Oracle addresses the issue in the Oracle Security Alert - October 2026
Technical Details for CVE-2026-91305
Vulnerability Analysis
The vulnerability resides in the Installation Security component of Oracle JD Edwards EnterpriseOne Tools. The weakness is categorized as Improper Authentication [CWE-287], indicating the component fails to correctly verify the identity of a requester before granting access to protected functionality. Oracle rates the issue with high confidentiality and integrity impact and no availability impact. The attack reaches the product over HTTPS, which means standard perimeter TLS protections do not mitigate the flaw.
Exploitation does not require credentials, privileges, or user interaction. An attacker with network reach to the HTTPS endpoint can invoke protected operations as if authenticated. The resulting access covers all data visible to JD Edwards EnterpriseOne Tools, which typically includes financial, supply chain, and human capital records in enterprise ERP deployments.
Root Cause
The Installation Security component does not sufficiently authenticate inbound HTTPS requests before authorizing privileged actions. Because the attack complexity is low and no privileges are required, the control path can be exercised directly by a remote caller. The absence of integrity controls on sensitive operations allows the attacker to create, delete, or modify records in addition to reading them.
Attack Vector
The attacker needs network access to the JD Edwards EnterpriseOne Tools HTTPS listener. From there, the attacker issues requests that the Installation Security component accepts without proper authentication. The attacker then reads sensitive ERP data or alters records to disrupt business processes, forge transactions, or stage follow-on fraud. No specific client code is required beyond an HTTPS client capable of reaching the vulnerable endpoint.
Oracle has not published exploitation details, and no public proof of concept is available at this time. The EPSS score is 0.377% as of 2026-10-22, reflecting a currently low observed exploitation probability.
Detect Identity Attacks the Moment Authentication Fails
Singularity™ Identity surfaces credential misuse, lateral movement, and privilege escalation in real time, so you can contain the breach before it spreads.
Stop Identity AttacksDetection Methods for CVE-2026-91305
Indicators of Compromise
- Unexpected HTTPS requests to JD Edwards EnterpriseOne Tools administrative or installation endpoints originating from unapproved source addresses.
- Audit log entries showing privileged create, update, or delete actions without a corresponding authenticated session.
- Anomalous data exports or bulk reads from JD Edwards tables outside of scheduled integration windows.
Detection Strategies
- Correlate web server access logs with JD Edwards application audit logs to identify requests that reach privileged routes without a prior successful authentication event.
- Baseline normal administrative traffic to the Installation Security component and alert on deviations in source, volume, or request pattern.
- Hunt for HTTP response codes indicating successful privileged operations following unauthenticated session identifiers.
Monitoring Recommendations
- Enable verbose logging on the JD Edwards EnterpriseOne Tools web tier and forward logs to a centralized analytics platform for retention and query.
- Monitor database audit trails for mass record modifications and unexpected schema or configuration changes.
- Alert on new administrative accounts, privilege changes, or integration endpoints created outside of approved change windows.
How to Mitigate CVE-2026-91305
Immediate Actions Required
- Apply the fixes delivered in the Oracle Security Alert - October 2026 to all JD Edwards EnterpriseOne Tools deployments running versions 9.2.0.0 through 9.2.26.5.
- Restrict network reachability of the JD Edwards EnterpriseOne Tools HTTPS interface to trusted management networks only.
- Review audit logs for the period preceding patch deployment to identify unauthenticated access attempts against installation and administrative endpoints.
Patch Information
Oracle addressed CVE-2026-91305 in the October 2026 Critical Patch Update. Administrators should consult the Oracle Security Alert - October 2026 for the exact patch bundle applicable to their JD Edwards EnterpriseOne Tools version. Oracle's standard guidance is to apply Critical Patch Update fixes without delay because unpatched products remain exposed to disclosed issues.
Workarounds
- Place the JD Edwards EnterpriseOne Tools HTTPS endpoints behind a reverse proxy or web application firewall that enforces authentication and rate limiting until the patch is deployed.
- Use network segmentation and firewall rules to limit inbound HTTPS access to known administrative hosts.
- Enforce multi-factor authentication for upstream identity providers that broker access to JD Edwards administrative functions.
# Example firewall restriction limiting access to the JD Edwards Tools HTTPS listener
iptables -A INPUT -p tcp --dport 443 -s 10.20.30.0/24 -j ACCEPT
iptables -A INPUT -p tcp --dport 443 -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

