Automated Threat Modeling

Quick Look: Oracle REST Data Services CVE-2026-114852, an Authenticated Data Access and Modification Flaw

A brief summary of CVE-2026-114852, a CVSS 8.1 flaw in the Core component of Oracle REST Data Services 24.2.0 through 26.3.0 that lets a low-privileged HTTP user read and alter ORDS accessible data. Includes patch information from Oracle's November 2026 Critical Security Patch Update.

CVE Analysis

7 min read

Gaurav Sarraf
Gaurav Sarraf

2026-11-17

Quick Look: Oracle REST Data Services CVE-2026-114852, an Authenticated Data Access and Modification Flaw

Introduction

Oracle's November 2026 advisory describes a flaw that lets an authenticated user with only basic privileges in Oracle REST Data Services (ORDS) read, create, change, or delete critical data that ORDS can reach. ORDS is the HTTP layer in front of Oracle Database for REST APIs, SQL Developer Web, and PL/SQL Gateway applications, so a weakness in its Core component maps directly onto the database data those services expose.

ORDS is a Java application from Oracle that bridges HTTPS and Oracle Database. It provides a Database Management REST API, SQL Developer Web, a PL/SQL Gateway, SODA for REST, and RESTful services over database tables and stored procedures. It sits inside Oracle's database ecosystem, which Oracle's own summary of the 2025 Gartner Critical Capabilities assessment ranks highest among 19 vendors for the OLTP Transactions use case. Independent reporting from The Register places Oracle third in DBMS revenue behind AWS and Microsoft since 2022. Neither figure counts ORDS installations. ORDS can run standalone on Jetty or inside Apache Tomcat or Oracle WebLogic Server, which makes it a common way to put Oracle data behind HTTP in many different hosting setups.

CVE-2026-114852 carries a CVSS 3.1 base score of 8.1 and is fixed in Oracle's November 2026 Critical Security Patch Update (CSPU).

Technical Information

What Oracle disclosed

Oracle's published vector is:

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N

Read against the CVSS v3.1 specification, this means:

  • Attack vector: Network. Oracle specifies HTTP. Network does not necessarily mean internet facing. The standard also covers attacks launched from a corporate intranet.
  • Attack complexity: Low. The rating reflects no special access conditions.
  • Privileges required: Low. The attacker needs a valid, basic-level account before exploitation. This is not an unauthenticated bug.
  • User interaction: None.
  • Scope: Unchanged. The impact stays within the same security authority, which is why Oracle frames consequences in terms of "ORDS accessible data" rather than every database or host in an environment.
  • Confidentiality: High. Unauthorized access to critical data or complete access to all ORDS accessible data.
  • Integrity: High. Unauthorized creation, deletion, or modification of critical data or all ORDS accessible data.
  • Availability: None. No availability impact is scored, even though deletion of data is explicitly in scope.

Root cause: what is known and what is not

No CWE is assigned, and the label "Core" identifies a component, not a root cause. Oracle has not published source code, a commit, or a diff, and the disclosure does not name the vulnerable endpoint, request format, parameter, payload, or internal code path.

What the impact profile does tell us is that an authenticated but low-privileged session can act on data outside its intended scope. That is consistent with a missing or incomplete authorization check, and the patch information we reviewed characterizes the fix as restoring that boundary. Oracle, however, has not said which check or code path changed. The evidence does not support describing this CVE as SQL injection, deserialization, authentication bypass, remote code execution, or operating system takeover, and we have no vulnerable code to show.

Attack flow

Based only on the published prerequisites and outcomes, an attack looks like this:

  1. Obtain a low-privileged identity. The attacker holds any account that ORDS accepts with low privileges. Oracle's baseline guidance (protect APIs with privileges and OAuth 2.0 clients, use HTTPS) does not prevent this bug, because the CVE already assumes the attacker is authenticated.
  2. Reach an ORDS listener over HTTP. This could be an exposed service or one reachable from inside the corporate network.
  3. Send crafted HTTP requests to ORDS. Complexity is low and no victim interaction is needed. The specific requests are not public.
  4. Read or alter data beyond the account's authority. The documented result is unauthorized read access to critical or all ORDS accessible data, plus the ability to create, modify, or delete it.

Exploitation status

The reviewed sources do not confirm exploitation in the wild. CISA KEV catalog version 2026.11.17 (released November 17, 2026, 17:53:15.5664 UTC) contained no entry for CVE-2026-114852. That is a bounded observation about one snapshot, not proof of no exploitation. We found no verified public proof of concept, no threat actor attribution, and no CVE-specific indicators. The 8.1 base score describes intrinsic characteristics and does not forecast exploit availability.

Patch Information

Oracle fixed CVE-2026-114852 in its November 2026 Critical Security Patch Update. Everything below comes from Oracle's advisory, its machine-readable CSAF record, and the ORDS release pages.

What the vendor fix covers

  • One of eight ORDS patches in the same bundle. The November 2026 CSPU lists eight new security patches for ORDS: this CVE, CVE-2026-114849 (9.8), CVE-2026-114856 (9.6), CVE-2026-114857 (8.8, PL/SQL Gateway), and four lower-scored Core issues. All eight share the 24.2.0 through 26.3.0 affected range. Applying the update for this CVE fixes the other seven as well. There is no separate hotfix for this bug alone.
  • Fix type and where to get it. Oracle's CSAF feed categorizes the remediation as vendor_fix for ORDS 24.2.0 through 26.3.0, available to "Oracle customers with valid support contracts." The advisory points to My Oracle Support patch availability document CPU431 (Database family) for the exact patch and installation steps.
  • What the fix has to stop. A low-privileged HTTP user reading, creating, changing, or deleting critical data that ORDS can reach. Oracle has not said which check or code path changed.

Which ORDS build to deploy

ORDS ships as a standalone versioned product, so the usual path is to move to a build above the affected range, which ends at 26.3.0. The current release is ORDS 26.3.1:

Version: 26.3.1 Build: 26.3.1.303.1615 Release: November 4, 2026 SHA1: b5282c026d310bc6a4c4967ed4d72ba0c316bf95 Java: Oracle Java and GraalVM 17, 21, 25

The 26.3.1 changelog does not mention CVE-2026-114852 or list any security fixes. Its "Issues Fixed" entries are functional, such as JWT/JWKS timeout error handling and extra logging for basic auth failures on /oauth2/token. Oracle publishes security fixes only through the CSPU, so treat 26.3.1 as the likely fixed build, not a confirmed one. Check it against CPU431 before relying on it, especially if you run a 24.x or 25.x branch and cannot upgrade straight to 26.3.1.

Verifying the fix

  1. Check the ORDS version on each node, using the ORDS version command or the version banner in the logs. Any build at 26.3.0 or below is still vulnerable.
  2. Compare your installed artifact against the hash on Oracle's download page.
  3. Restart every ORDS instance, including standalone Jetty nodes and deployments in WebLogic or Tomcat. The old code stays in memory until the restart.
  4. Because exploitation requires a valid login, make sure your validation tests include requests made as a low-privileged REST user. Smoke tests run only as an administrator will miss it.

Interim measures

Oracle's general guidance for the period before patching is to block network protocols an attack requires (HTTP for this CVE) and remove privileges or package access from users who do not need them, testing changes in a nonproduction environment first. These steps may break functionality and are not a disclosed complete workaround for this CVE. Oracle states they are not a permanent solution.

Affected Systems and Versions

  • Product: Oracle REST Data Services, Core component.
  • Affected supported versions: 24.2.0 through 26.3.0 inclusive. Running 26.3.0 does not place a deployment outside the range.
  • Deployment modes: The issue is in ORDS itself, whether it runs standalone on Jetty or inside Apache Tomcat or Oracle WebLogic Server. Hosting choice does not make this a Tomcat or WebLogic vulnerability.
  • Exposure condition: An attacker must hold a low-privileged account accepted by ORDS and reach the ORDS HTTP listener over the network.
  • Likely fixed build: ORDS 26.3.1 (build 26.3.1.303.1615), pending confirmation against CPU431.

Vendor Security History

This is not the first ORDS disclosure in 2026:

  • CVE-2026-35277 (May 28, 2026): affected 24.2.0 through 26.1.0, CVSS 3.1 8.1, unauthorized access to and modification of ORDS accessible data.
  • CVE-2026-46839 (May 28, 2026): affected 24.2.0 through 26.1.0, CVSS 3.1 9.9, ORDS takeover with potential significant impact on additional products.
  • CVE-2026-114852 (November 17, 2026): affected 24.2.0 through 26.3.0, CVSS 3.1 8.1, unauthorized access to and modification of ORDS accessible data.

The earlier disclosures show different impact profiles within the same product. They do not establish a common root cause, a bypass of a prior fix, or exploitation of the current CVE. Together with the seven other ORDS fixes in the November bundle, they indicate that ORDS needs regular maintenance like any other internet-adjacent service.

Oracle runs quarterly Critical Patch Updates, emergency Security Alerts, and risk-based remediation, and its November advisory describes security patch releases on the third Tuesday of each month. Oracle also reports successful attacks against customers who had not applied already available patches, though it does not tie those incidents to this CVE.

References

Detect & fix
what others miss

Works with
  • GitHub
  • GitLab
  • Bitbucket
  • Azure DevOps Services
  • Gerrit
  • CVS
  • Jira
  • Linear
  • Slack
  • Security Compass
Explore integrations
Security magnifying glass visualization