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-91623 Overview
CVE-2026-91623 affects Oracle Agile Product Lifecycle Management for Process version 6.2.4, specifically the Product Quality Management component. The flaw lets an unauthenticated attacker with network access over HTTP compromise the application. Successful exploitation grants unauthorized create, delete, or modify access to critical data and read access to all data accessible through the product. Oracle rates the issue as difficult to exploit, which is reflected in the high attack complexity. The vulnerability was published in the Oracle Critical Patch Update advisory of October 2026.
Critical Impact
An unauthenticated network attacker can read, modify, or delete all data accessible to Oracle Agile Product Lifecycle Management for Process.
Affected Products
- Oracle Supply Chain – Agile Product Lifecycle Management for Process
- Component: Product Quality Management
- Affected version: 6.2.4
Discovery Timeline
- 2026-10-20 - CVE-2026-91623 published to NVD
- 2026-10-21 - Last updated in NVD database
- October 2026 - Addressed in the Oracle Security Alert October 2026
Technical Details for CVE-2026-91623
Vulnerability Analysis
The vulnerability resides in the Product Quality Management component of Oracle Agile Product Lifecycle Management for Process 6.2.4. An attacker reaches the vulnerable code path over HTTP without any authentication or user interaction. Successful exploitation yields full read access to data handled by the application and the ability to create, modify, or delete that data. Availability is not directly impacted, but integrity loss in a product quality system can cascade into manufacturing, compliance, and supply chain decisions.
Oracle characterizes exploitation as difficult, indicating that specific conditions outside the attacker's control must be met. The confidentiality and integrity impacts, however, span the entire data scope of the product. The EPSS probability stands at 0.341% with a percentile of 26.365, reflecting a low near-term likelihood of mass exploitation at publication time.
Root Cause
Oracle has not disclosed the underlying weakness class, and no CWE identifier is assigned in the NVD record. Based on the impact profile, which combines unauthenticated network reach with broad data compromise, the defect likely involves missing authorization or improper input handling in an HTTP-exposed interface of the Product Quality Management component.
Attack Vector
The attack vector is network-based over HTTP. No credentials and no user interaction are required. The attacker needs reachability to the Oracle Agile PLM for Process web interface and must satisfy the conditions that make the exploit non-trivial. Oracle has not released public exploit details, and no proof-of-concept has been observed.
See the Oracle Security Alert October 2026 for the vendor's technical summary.
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-91623
Indicators of Compromise
- Unexpected creation, modification, or deletion of Product Quality Management records authored by service or anonymous accounts.
- Anomalous HTTP requests to Agile PLM for Process endpoints originating from untrusted networks.
- Spikes in outbound data transfers from the Agile PLM application server.
Detection Strategies
- Enable verbose HTTP access logging on the Agile PLM for Process application server and review for unauthenticated requests to Product Quality Management paths.
- Correlate database audit logs with application-level authentication events to identify data changes without a corresponding authenticated session.
- Deploy a web application firewall rule to log and alert on malformed or unusual request parameters targeting the component.
Monitoring Recommendations
- Baseline normal volumes of create, update, and delete operations in Product Quality Management and alert on deviations.
- Monitor file integrity on configuration and deployment directories of the Agile PLM for Process installation.
- Forward application, web server, and database logs to a central analytics platform to support cross-source hunting.
How to Mitigate CVE-2026-91623
Immediate Actions Required
- Apply the fixes delivered in the Oracle Critical Patch Update of October 2026 to all Oracle Agile Product Lifecycle Management for Process 6.2.4 deployments.
- Restrict network access to the Agile PLM for Process web tier to trusted corporate segments and VPN users only.
- Review Product Quality Management audit trails for unauthorized data changes made before patching.
Patch Information
Oracle published remediation guidance in the Oracle Security Alert October 2026. Administrators should follow Oracle's documented patch sequence for Supply Chain products and validate the fix in a non-production environment before rolling out.
Workarounds
- Place the Agile PLM for Process web interface behind a reverse proxy that enforces authentication at the perimeter.
- Block external HTTP and HTTPS access to the application until the patch is deployed.
- Tighten database-level permissions used by the application service account to the minimum required for its operations.
# Example: restrict inbound HTTP/HTTPS to Agile PLM for Process using iptables
iptables -A INPUT -p tcp --dport 443 -s 10.0.0.0/8 -j ACCEPT
iptables -A INPUT -p tcp --dport 443 -j DROP
iptables -A INPUT -p tcp --dport 80 -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

