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-91609 Overview
CVE-2026-91609 is a vulnerability in Oracle REST Data Services (ORDS), specifically within the GraphQL component. The flaw affects supported versions 24.2.0 through 26.2.1. A low-privileged attacker with network access over HTTP can exploit this issue to gain unauthorized access to critical data or complete read access to all data accessible through ORDS. Oracle disclosed the issue in the October 2026 Critical Patch Update advisory. Exploitation does not require user interaction, and the attack complexity is low, making it a priority fix for organizations exposing ORDS endpoints to internal or external networks.
Critical Impact
An authenticated low-privileged attacker can read all data accessible through Oracle REST Data Services via the GraphQL interface, leading to disclosure of sensitive database contents.
Affected Products
- Oracle REST Data Services 24.2.0 through 26.2.1
- GraphQL component of Oracle REST Data Services
- Any Oracle Database environment exposing data via ORDS GraphQL endpoints
Discovery Timeline
- 2026-10-20 - CVE-2026-91609 published to the National Vulnerability Database
- 2026-10-21 - Last updated in NVD database
- October 2026 - Oracle addresses the issue in the October 2026 Critical Patch Update (Oracle Security Alert October 2026)
Technical Details for CVE-2026-91609
Vulnerability Analysis
The vulnerability resides in the GraphQL component of Oracle REST Data Services, the middle-tier Java application that exposes Oracle Database objects as RESTful and GraphQL endpoints. An attacker with any authenticated low-privileged ORDS account can issue crafted GraphQL requests over HTTP to retrieve data outside the intended authorization boundary. The confidentiality impact is high, while integrity and availability are unaffected. Oracle's advisory classifies this as an easily exploitable issue, meaning no advanced tooling or chained conditions are required. The current EPSS probability is 0.371% at percentile 29.834, reflecting limited observed exploitation activity so far.
Root Cause
The root cause is improper authorization enforcement within the GraphQL query handler. The component evaluates incoming queries without correctly scoping access checks to the authenticated user's privilege level. This is consistent with a GraphQL API authorization flaw where field-level or type-level access controls are missing or inconsistently applied. Oracle has not published a specific CWE classification for this entry.
Attack Vector
Exploitation requires network reachability to an ORDS instance exposing the GraphQL endpoint and valid low-privileged credentials. The attacker authenticates, submits GraphQL queries referencing objects or fields that should be inaccessible, and the GraphQL resolver returns the data without rejecting the request. No social engineering or client-side interaction is involved. Internet-exposed ORDS deployments and multi-tenant database environments are at highest risk because low-privileged accounts are commonly provisioned and attacker reconnaissance of GraphQL schemas is straightforward.
The vulnerability manifests in the GraphQL query authorization path within ORDS. No verified proof-of-concept code is available publicly. Refer to the Oracle Security Alert October 2026 for vendor technical guidance.
Detection Methods for CVE-2026-91609
Indicators of Compromise
- Unexpected HTTP POST requests to ORDS GraphQL endpoints (typically /ords/*/graphql or module-specific GraphQL paths) from low-privileged accounts
- GraphQL queries that enumerate schema introspection (__schema, __type) followed by targeted queries for sensitive fields
- Large volumes of GraphQL responses returning fields that the authenticated user should not have access to
- Access patterns from service accounts querying tables outside their business function
Detection Strategies
- Enable ORDS request logging and parse GraphQL request bodies for anomalous field selections referencing restricted objects
- Correlate ORDS access logs with Oracle Database audit trails to identify queries that bypass expected authorization boundaries
- Alert on GraphQL introspection queries from accounts that have no documented application need to perform schema discovery
Monitoring Recommendations
- Forward ORDS and Oracle Database audit logs to a centralized SIEM for behavioral analysis of GraphQL activity
- Baseline normal GraphQL query patterns per user role and alert on deviations in query depth, selected fields, or response size
- Monitor authentication events for low-privileged ORDS accounts showing sudden increases in GraphQL endpoint usage
How to Mitigate CVE-2026-91609
Immediate Actions Required
- Apply the fixes from the Oracle October 2026 Critical Patch Update to all ORDS instances running versions 24.2.0 through 26.2.1
- Inventory all ORDS deployments and confirm whether the GraphQL component is enabled, since not every ORDS installation exposes GraphQL
- Restrict network access to ORDS endpoints behind a reverse proxy or WAF and limit exposure to only required consumers
- Review and reduce the number of low-privileged ORDS accounts, rotating credentials for any accounts that may have been abused
Patch Information
Oracle has released fixed versions as part of the October 2026 Critical Patch Update. Refer to the Oracle Security Alert October 2026 for exact patch version numbers and installation instructions. Patching is the only complete remediation for this vulnerability.
Workarounds
- Disable the GraphQL feature in ORDS configuration if the application does not require it
- Enforce stricter database-level privileges on accounts used by ORDS so that even bypassed authorization yields no sensitive data
- Place ORDS behind an authenticating reverse proxy that enforces IP allowlists for GraphQL endpoints until patches are applied
# Example: disable the GraphQL feature in ORDS until patched
# Edit the ORDS configuration and set the feature flag to false
ords --config /path/to/ords/config config set feature.graphql false
ords --config /path/to/ords/config stop
ords --config /path/to/ords/config start
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

