Introduction
Oracle's November 2026 Critical Security Patch Update fixes a flaw in the PL/SQL Gateway of Oracle REST Data Services (ORDS) that allows a low-privileged attacker with HTTP access to take over the ORDS service. ORDS is the layer that brokers web requests into Oracle Database, so a takeover of that layer matters. Oracle scores it 8.8, with high confidentiality, integrity and availability impact.
ORDS is a Java application from Oracle that bridges HTTP requests and Oracle Database. It provides a PL/SQL Gateway along with services for working with database data and stored procedures. Oracle offers it for both on-premises and Oracle Cloud deployments, with standalone Jetty, Tomcat and WebLogic Server deployment options. The public sources we reviewed do not provide verified usage or market share figures for ORDS itself. Its relevance comes from its position inside Oracle's broader database, cloud and enterprise application portfolio, where it is an integration component rather than a single application interface.
Technical Information
Affected component
Oracle's advisory and its text-form risk matrix identify the affected product as Oracle REST Data Services and the component as PL/SQL Gateway. Oracle attributes the vulnerability to ORDS, not to Oracle APEX or to Oracle Database in general. Both Oracle and NVD list the affected supported range as 24.2.0 through 26.3.0. The supplied CVE data lists the vendor as Unknown, but the CVE record identifies Oracle Corporation.
Published severity
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H Base score: 8.8 (High)
| Metric | Value | What it means here |
|---|---|---|
| Attack Vector | Network (AV:N) | Network access is required. Oracle names HTTP as the protocol. |
| Attack Complexity | Low (AC:L) | Oracle describes the flaw as easily exploitable. |
| Privileges Required | Low (PR:L) | Some privileges are needed, so this is not an unauthenticated issue. |
| User Interaction | None (UI:N) | No victim action is required. |
| Scope | Unchanged (S:U) | Oracle does not assign changed scope. |
| Confidentiality | High (C:H) | High impact. |
| Integrity | High (I:H) | High impact. |
| Availability | High (A:H) | High impact. |
The notable combination is a low-privilege prerequisite paired with a stated outcome of full ORDS takeover.
Root cause: what is and is not disclosed
Oracle has not published a root cause. The reviewed records do not disclose the vulnerable code path, the request handler or stored procedure involved, a request payload, the exact endpoint, or the account role an attacker needs. NVD provides no CWE identifier. ORDS is closed source, so there is no public commit or diff to examine.
Because of this, we cannot responsibly classify the bug as SQL injection, authentication bypass, deserialization, or any other specific weakness class, and we are not reproducing any code here. Similarly, the published impact is takeover of ORDS. The description does not establish operating system compromise, compromise of every connected database, or a specific remote code execution primitive, and those outcomes should not be substituted for Oracle's wording.
Attack flow from published conditions
The following sequence reflects only what Oracle and NVD state about prerequisites and outcome:
- The attacker has network reachability to an ORDS instance running a version between 24.2.0 and 26.3.0, over HTTP.
- The attacker holds low privileges. Which account type or role is sufficient has not been disclosed.
- The attacker sends requests that the PL/SQL Gateway component processes. No user interaction is required, and attack complexity is rated low.
- Successful exploitation results in takeover of Oracle REST Data Services, with high impact to confidentiality, integrity and availability.
This is enough to scope exposure and prioritize patching, but not enough to reconstruct a reliable exploit or to assume that any particular account type is or is not sufficient.
Exploitation status
| Question | Finding | Limitation |
|---|---|---|
| Is active exploitation confirmed? | Not confirmed in the reviewed CVE-specific material. | Absence of confirmation is not proof of no attacks. |
| Is a threat actor attributed? | No CVE-specific attribution found. | Historical Oracle campaigns cannot supply attribution here. |
| Is there verified public exploit code? | None in the reviewed records. | Code may exist elsewhere. |
| Is it in CISA KEV? | Not in the KEV JSON snapshot dated 17 November 2026. VulDB also records KEV status as no. | A snapshot is a point-in-time view. |
| Are CVE-specific indicators available? | None supplied. | Indicators for other Oracle CVEs are not interchangeable. |
Under the CVSS 3.1 specification, the 8.8 base score describes intrinsic technical severity. Exploit maturity is a separate temporal consideration, so the score alone does not imply an active campaign.
Patch Information
Oracle fixed CVE-2026-114857 in its Critical Security Patch Update (CSPU) for November 2026, released on 17 November 2026 (Rev 1, initial release). The CVE appears in the advisory's Oracle REST Data Services Risk Matrix, which states that the update contains 8 new security patches for ORDS. One of them addresses this flaw in the PL/SQL Gateway.
| Field | Value (from Oracle's advisory and CSAF) |
|---|---|
| Product / component | Oracle REST Data Services / PL/SQL Gateway |
| Affected supported versions | 24.2.0 through 26.3.0 |
| Oracle Bug ID | 40092444 |
| Remediation category (CSAF) | vendor_fix |
| Patch delivery | My Oracle Support document CPU431 |
| Who can get it | Oracle customers with valid support contracts |
| Severity being fixed | CVSS 3.1 8.8 (AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H) |
How to read Oracle's patch evidence
Oracle's publications work at two levels:
- The advisory and risk matrix (advisory, text form) confirm that the CVE belongs to this patch cycle, give the affected range and component, and link patch availability to the Database family document CPU431.
- The machine-readable CSAF file is more precise. It ties the CVE to internal bug 40092444 and records a formal vendor_fix remediation pointing to CPU431. The bug ID is the practical handle for locating the exact patch in My Oracle Support and for verifying installation, since patch READMEs and inventory tools usually list fixed bug numbers.
Fixed version is not stated publicly
Neither the CSAF entry nor the advisory page names a fixed ORDS build. The CSAF lists the product only as known_affected (Oracle REST Data Services Version 24.2.0 through 26.3.0), with no matching fixed product ID. In practice:
- Treat any ORDS deployment from 24.2.0 through 26.3.0 as vulnerable until the November 2026 CSPU content from CPU431 is applied.
- Get the exact build or patch number for each release line from the CPU431 support document, which requires a login. Do not infer it from the version range.
- After patching, confirm that bug 40092444 appears among the fixes in the installed patch or release.
Some sources that surfaced during research do not describe this fix, including Microsoft and Red Hat bulletins, an unrelated EUVD entry for a Horizon DataSys driver, and a claimed GitHub patch advisory. Oracle's advisory and CSAF are the authoritative patch evidence.
Interim measures and their limits
Oracle's advisory describes two general measures that may reduce risk until patches are applied:
- Block the network protocols an attack requires. For this CVE that protocol is HTTP. Oracle has not published a narrower request pattern or CVE-specific blocking rule.
- Remove unnecessary privileges or package access where an attack depends on them. Oracle has not identified the specific privilege or package for this issue.
Oracle warns that both may break application functionality, recommends testing on nonproduction systems, and is explicit that neither corrects the underlying vulnerability.
The PL/SQL Gateway also supports a request validation function that receives the requested resource name and returns TRUE or FALSE, with ORDS terminating the request on FALSE. Oracle documents a custom validation function that allowlists permitted stored procedures for production use. This is sound general gateway hardening, but the documentation does not establish it as a workaround for CVE-2026-114857, and the sources likewise do not establish that moving to HTTPS resolves the issue. The corrective action remains the Oracle patch.
Affected Systems and Versions
- Product: Oracle REST Data Services
- Component: PL/SQL Gateway
- Affected supported versions: 24.2.0 through 26.3.0 (an affected range, not a list of fixed releases)
- Vulnerable condition: an affected ORDS instance reachable over HTTP by an attacker holding low privileges
- Fixed build: not publicly named; consult CPU431 and verify bug 40092444
Oracle's fixing policy states that it does not provide fixes for out-of-support product versions. A release that falls outside the listed supported range should therefore not be assumed safe simply because it is not named.
Vendor Security History
Oracle's record includes a documented incident in a different product and CVE. Google Threat Intelligence Group reported a 2025 Oracle E Business Suite campaign, possibly involving CVE-2025-61882, in which some victims experienced exfiltration of significant amounts of data and a threat actor claimed affiliation with the CL0P extortion brand. Google noted tooling and branding overlaps but did not formally attribute the activity to a tracked group. Oracle released an emergency patch for CVE-2025-61882 on 4 October 2025, and its security alert described unauthenticated exploitation that may result in remote code execution.
That case shows Oracle will ship out-of-schedule fixes for critical or actively exploited issues, consistent with its published fixing policy. It also illustrates a point Oracle itself makes: successful attacks have occurred against customers who had not applied available patches. It does not imply that the same actors, exploit chain or impact apply to ORDS. The EBS issue was unauthenticated with confirmed exploitation, while CVE-2026-114857 requires low privileges and has no confirmed campaign.
References
- NVD entry for CVE-2026-114857
- CVE Record for CVE-2026-114857
- Oracle Critical Security Patch Update Advisory, November 2026
- Text Form of Oracle CSPU November 2026 Risk Matrices
- Oracle CSPU November 2026 CSAF file
- My Oracle Support document CPU431
- Oracle REST Data Services product page
- ORDS PL/SQL Gateway documentation
- Oracle Security Fixing Policies
- About Oracle
- CVSS v3.1 Specification Document
- CISA Known Exploited Vulnerabilities Catalog
- CISA KEV JSON feed
- VulDB entry for CVE-2026-114857
- Oracle Security Alert for CVE-2025-61882
- NCSC: Active exploitation of vulnerability affecting Oracle E Business Suite
- Google Cloud Blog: Oracle E Business Suite exploitation in extortion campaign



