Oracle's October 2026 advisory says a low-privilege user with HTTP network access can reach critical data, potentially all data accessible to ORDS. The advisory scores this individual flaw 6.5 under CVSS 3.1.Depthfirst separately describes a research chain that combines this GraphQL access path with CVE-2026-114819 in Oracle AI Database. The researcher says the combined chain can reach operating-system command execution from an exposed HTTP interface without authentication. That outcome belongs to the two-flaw chain; Oracle does not attribute command execution to CVE-2026-91609 alone.
What it allows
What Does CVE-2026-91609 Allow?
Oracle identifies the vulnerable component as GraphQL in ORDS. Its matrix lists HTTP as the protocol, low privileges as required, and high confidentiality impact. The vendor describes unauthorized access to critical data or all ORDS-accessible data, without assigning integrity or availability impact to this CVE.
Depthfirst says the October GraphQL flaw supplies an access path into its separate Oracle AI Database flaw, CVE-2026-114819. The researcher describes a crafted document reaching database engine code and then command execution as the database service user. This is the researcher's demonstrated chain, not a claim that the GraphQL flaw alone executes commands or that an intrusion has occurred.
Our defensive reading is to inventory exposed ORDS GraphQL deployments and the database servers behind them as one path. Use the Vulnerability Intelligence platform to track the separate advisories and their patch decisions. Oracle's November patch matrix coverage provides context for the second CVE, while the October ORDS fix addresses this entry point.
Who is affected
Which ORDS Versions Are Affected by CVE-2026-91609?
Oracle lists supported ORDS versions 24.2.0 through 26.2.1 as affected by this GraphQL flaw. The row says remote exploitation without authentication is not available for this CVE on its own. Prioritize deployments with reachable GraphQL HTTP interfaces and low-privilege users, then check their actual ORDS release and patch level.
The October advisory includes the fix and points to Oracle's patch availability document for installation instructions. Its product-family heading includes 26.2.2 because the update covers multiple ORDS CVEs; do not use that heading as a substitute for this CVE's affected-version row. Confirm the installed ORDS build and applied October security update against Oracle's patch documentation, including any vendor-managed deployment.
The research chain also depends on CVE-2026-114819 in the Oracle Database Server. Oracle's November matrix lists affected server ranges 19.3 to 19.32, 21.3 to 21.24 and 23.4.0 to 23.26.3 for that separate flaw. Assess both products independently and record the results in the patch management process.
Timeline
-
2026-10-20
NVD published Oracle's description of CVE-2026-91609; Oracle's October Critical Patch Update includes the ORDS GraphQL risk-matrix entry.
-
2026-11-18
Depthfirst published its two-CVE research chain involving CVE-2026-91609 and CVE-2026-114819; Oracle's November update lists the latter flaw.
What to do
-
Inventory the access path
Identify ORDS instances exposing GraphQL over HTTP, the connected Oracle Database Server versions, and the roles allowed to use the interface.
-
Apply the October ORDS fix
Follow Oracle's October 2026 Critical Patch Update and its ORDS patch availability document for CVE-2026-91609. Restrict unnecessary GraphQL exposure while maintenance is scheduled.
-
Apply the separate November database fix
Check each connected database server against Oracle's CVE-2026-114819 November matrix and install the applicable server security patch.
-
Verify the running builds
After maintenance, confirm the running ORDS build carries the October fix and the connected database server carries the November fix. Retain vendor patch records for managed or backported deployments.
-
Review relevant activity
Review available ORDS GraphQL access records and database audit logs for unexpected low-privilege data access. This is defensive triage guidance, not a published detection signature.
What Brandefense can do
- Watch your stack for exploited flaws
Name the vendors and products you run, and Brandefense alerts you when a CVE in them is exploited.
- See CVE-2026-91609 in Brandefense Atlas
The Atlas record of CVE-2026-91609: severity, exploitation status and the sources behind it.
- Vulnerability intelligence platform
Brandefense Vulnerability Intelligence follows which vulnerabilities attackers are using, so your team can patch what is under attack first.
Frequently Asked Questions
Does CVE-2026-91609 alone allow unauthenticated code execution?
Oracle describes a low-privilege HTTP data exposure flaw. Depthfirst attributes unauthenticated command execution to a research chain that also needs CVE-2026-114819.
Which ORDS releases does Oracle list as affected?
Oracle's October risk matrix lists supported ORDS versions 24.2.0 through 26.2.1. Confirm the installed security update with Oracle's patch availability documentation.
Why check the database server after patching ORDS?
The published chain joins the ORDS entry point with a separate Oracle Database Server flaw. Assess and patch CVE-2026-114819 independently under Oracle's November advisory.
Sources
- October 2026 Critical Patch UpdateOracle
- November 2026 Critical Security Patch UpdateOracle
- Narrow Grants, Wide EnginesDepthfirst
- CVE-2026-91609NIST National Vulnerability Database