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-101367 Overview
CVE-2026-101367 is a vulnerability in Oracle REST Data Services (ORDS) affecting the Advanced Data Protection (ADP) component. The flaw impacts supported versions 24.2.0 through 26.1.0. An authenticated attacker with low privileges can exploit the issue remotely over HTTP without user interaction.
Successful exploitation allows unauthorized modification of a subset of ORDS-accessible data through update, insert, or delete operations. Attackers can also obtain unauthorized read access to a limited portion of ORDS-accessible data. Oracle addressed the vulnerability in the October 2026 Critical Patch Update.
Critical Impact
An authenticated remote attacker can modify and read a subset of Oracle REST Data Services data without any user interaction, undermining data integrity and confidentiality in deployments running versions 24.2.0 through 26.1.0.
Affected Products
- Oracle REST Data Services version 24.2.0
- Oracle REST Data Services versions through 26.1.0
- Oracle REST Data Services ADP (Advanced Data Protection) component
Discovery Timeline
- 2026-10-20 - CVE-2026-101367 published to the National Vulnerability Database (NVD)
- 2026-10-21 - Last updated in NVD database
- October 2026 - Oracle released the fix in the Oracle Critical Patch Update October 2026
Technical Details for CVE-2026-101367
Vulnerability Analysis
Oracle REST Data Services (ORDS) is a Java-based middle-tier service that maps HTTP requests to SQL and PL/SQL operations against Oracle Database. The ADP component handles data protection functions exposed through the REST interface.
The vulnerability allows a low-privileged authenticated user to perform unauthorized data operations through HTTP requests. The impact spans both integrity and confidentiality, with no effect on availability. Attack complexity is low, meaning no specialized conditions are required to trigger the issue.
Because ORDS commonly sits between internet-facing applications and backend Oracle Databases, exploitation can affect data accessed through APIs built on ORDS. The scope remains unchanged, so impact is bounded by the privileges available to the authenticated session.
Root Cause
Oracle has not published detailed root-cause information. The advisory classifies the issue within the ADP component of ORDS and identifies it as a broken access control condition where low-privileged accounts can perform operations beyond their intended authorization boundary.
Attack Vector
The attack requires network access over HTTP and valid low-privileged credentials for the ORDS instance. No user interaction is required. An attacker sends crafted HTTP requests to ORDS endpoints exposed by the ADP component, triggering unauthorized read, insert, update, or delete operations against a subset of accessible data.
Refer to the Oracle Critical Patch Update October 2026 for Oracle's technical description and patch references.
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-101367
Indicators of Compromise
- Unexpected HTTP requests from low-privileged ORDS accounts targeting ADP component endpoints.
- Database audit records showing insert, update, or delete operations originating from ORDS sessions that lack a legitimate business reason.
- Anomalous volume of REST API calls to ORDS from a single authenticated identity in short time windows.
Detection Strategies
- Enable ORDS access logging and forward logs to a centralized analytics platform for correlation with database audit events.
- Baseline normal ORDS request patterns per user role and alert on deviations in endpoint access, HTTP methods, or payload size.
- Correlate authentication events with downstream SQL operations to identify privilege boundary violations.
Monitoring Recommendations
- Monitor Oracle Database audit trails for unexpected DML operations initiated through the ORDS service account.
- Track HTTP 2xx responses on ADP endpoints that previously returned 401 or 403 for the same identity, which may indicate exploitation.
- Alert on changes to ORDS configuration files and privilege grants on schemas exposed through REST endpoints.
How to Mitigate CVE-2026-101367
Immediate Actions Required
- Apply the October 2026 Oracle Critical Patch Update to all ORDS instances running affected versions 24.2.0 through 26.1.0.
- Inventory ORDS deployments and confirm the installed version using ords --version or the admin console.
- Audit all ORDS user accounts and remove unused low-privileged credentials that could be abused for exploitation.
- Review ORDS access logs for the past 90 days to identify suspicious activity against ADP endpoints.
Patch Information
Oracle released patches as part of the Critical Patch Update for October 2026. Administrators should download and apply the ORDS updates documented in the Oracle Critical Patch Update October 2026 advisory. Oracle recommends staying on supported release trains and applying CPUs promptly after release.
Workarounds
- Restrict network access to ORDS endpoints to known client subnets using firewall rules or a reverse proxy ACL.
- Enforce strong authentication and multi-factor authentication (MFA) for all ORDS accounts to raise the exploitation barrier.
- Disable or restrict the ADP component endpoints if they are not required for business operations.
- Apply least-privilege principles to ORDS-mapped database schemas, limiting the data accessible to low-privileged accounts.
# Verify installed ORDS version and check status
ords --version
ords config list
# Restrict ADP endpoint access at the reverse proxy (NGINX example)
# location /ords/adp/ {
# allow 10.0.0.0/8;
# deny all;
# proxy_pass http://ords_backend;
# }
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

