Introduction
Oracle REST Data Services sits directly in front of Oracle Database in many environments, exposing REST APIs, SQL Developer Web and the PL/SQL gateway over HTTPS. A flaw that lets an unauthenticated attacker take over that gateway, with impact Oracle says can extend to additional products, matters well beyond a single web tier.
ORDS is a Java application that bridges HTTPS and Oracle Database. It publishes RESTful services for database data and stored procedures, database management APIs and web-based development interfaces, and it is also the gateway for Oracle APEX and Oracle Database Actions. It runs on Oracle WebLogic Server, Apache Tomcat or standalone, in both customer premises deployments and Oracle Cloud Infrastructure instances. Its reach follows Oracle's database footprint: DB Engines ranks Oracle first in its November 2026 database popularity ranking, although that ranking measures popularity rather than the number of ORDS installations.
CVE-2026-114856 was published on November 17, 2026 as part of Oracle's November 2026 Critical Security Patch Update (CSPU), with a CVSS 3.1 base score of 9.6. This post summarizes what Oracle has disclosed, what it has left out, and how the fix is delivered.
Technical information
What Oracle disclosed
Oracle describes an easily exploitable vulnerability in the General component of ORDS. An unauthenticated attacker with network access over HTTPS can compromise ORDS, but successful attacks require interaction from a person other than the attacker. The stated outcome is takeover of Oracle REST Data Services, and because scope is changed, attacks may significantly impact additional products. The flaw is in ORDS itself, not in the database underneath it.
The published vector is:
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H
Reading it metric by metric:
- AV:N (Network): reachable over the network. Oracle names HTTPS as the protocol.
- AC:L (Low): Oracle characterizes the issue as easily exploitable.
- PR:N (None): the attacker needs no authentication.
- UI:R (Required): a person other than the attacker must participate.
- S:C (Changed): the impacted component can differ from the vulnerable one. Oracle warns of significant impact on additional products.
- C:H / I:H / A:H: high confidentiality, integrity and availability impact.
PR:N and UI:R are separate prerequisites, and both can hold at once. The attacker needs no account, but someone else has to act. Per FIRST's CVSS v3.1 specification, the base score reflects intrinsic severity under reasonable worst-case assumptions. It is not evidence that an attack has occurred.
Root cause: not public
ORDS is closed source, so there is no public commit, diff or pull request for this bug, and Oracle does not disclose detailed security analysis through its advisories. Oracle has not published a CWE, NVD lists no CWE, and VulDB lists the weakness classification as "Unknown". The Oracle CVE metadata provides a narrative description rather than a numeric CWE.
An unauthenticated attacker, required action by another user and changed scope together usually point to request or response handling where a victim's session is abused. This is an inference from the vector, not a confirmed root cause. Likewise, "takeover" should not be expanded into a claim about a particular remote code execution technique without further evidence.
Attack flow, as far as the disclosure supports
Based only on Oracle's description, the exploitation conditions are:
- The attacker has network access to an ORDS instance over HTTPS.
- The attacker holds no credentials for ORDS.
- A person other than the attacker performs some action that the attack depends on. Oracle does not describe what that action is.
- A successful attack results in takeover of ORDS, and because scope is changed, additional products may be significantly impacted.
ORDS is the HTTPS gateway to Oracle Database, APEX and Database Actions, so a takeover of it deserves more attention than a takeover of a standalone web page would. The disclosure does not establish which database privileges or downstream applications an attacker would obtain in any particular installation.
The public record leaves out the vulnerable endpoint, the triggering request, a payload, the precise victim action and the underlying execution primitive. Those gaps limit how precise this analysis can be. They do not lower the published 9.6 severity.
Exploitation status
The public material we reviewed did not establish any confirmed active exploitation, named threat actor or campaign targeting CVE-2026-114856. VulDB repeats the attack conditions without a public exploit implementation or attribution, and no CVE-specific indicators such as files, domains or request signatures have been published. VulDB marks CISA KEV membership as "no", but the CISA catalog view we could retrieve was a paginated subset, so KEV status is best described as unconfirmed. Read the status as "exploitation status unconfirmed", not "known unexploited".
Patch information
How the fix is delivered. Oracle shipped the fix in its November 2026 Critical Security Patch Update, published November 17, 2026. In the advisory's Oracle REST Data Services risk matrix, CVE-2026-114856 is one of 8 new security patches for ORDS. Its row reads: component General, protocol HTTPS, remotely exploitable without authentication Yes, CVSS 3.1 base score 9.6, affected supported versions 24.2.0 through 26.3.0.
Oracle does not put download links in the advisory. For ORDS, the patch availability column points to the "Database" patch availability document on My Oracle Support (MOS), and that MOS document is where Oracle names the patched builds.
Which build carries the fix. The public advisory does not name a fixed version. It only marks 24.2.0 through 26.3.0 as affected. Oracle's public ORDS download page currently offers ORDS 26.3.1 (build 26.3.1.303.1615), which supports Oracle Java 17, 21 and 25 and Oracle GraalVM Enterprise Edition for Java 17, 21 and 25. That page was last updated November 4, 2026. Version 26.3.1 is the first release above the affected range, but nothing public explicitly ties it to CVE-2026-114856. Use the MOS "Database" patch availability document to confirm the build before treating it as fixed. Third-party trackers such as InfraStack also note that the exact fixed ORDS version is not on Oracle's public page.
Upgrading fixes several CVEs at once. Oracle patched this CVE alongside other ORDS issues in the same CSPU, such as CVE-2026-114851, CVE-2026-114852, CVE-2026-114855 and CVE-2026-114857 (one of them a PL/SQL Gateway flaw). Moving to the CSPU-patched ORDS build should close all of them, not only this one.
After upgrading, check the running version:
java -jar ords.war version
The result should be above 26.3.0 and match what the MOS document lists.
Deployment notes from Oracle's guidance:
- Oracle's ORDS best practices recommend validating updates in preproduction and test environments before production.
- Oracle says blocking network protocols required by an attack may reduce risk until patches are applied, but such restrictions can break application functionality and do not correct the underlying problem. Test any workaround on systems outside production.
- General ORDS hardening (avoiding accidentally public APIs, planning authentication and authorization early, using privileges and OAuth 2.0 clients) is complementary and is not a demonstrated workaround for this CVE. HTTPS is also not a fix here, since HTTPS is the attack protocol.
Affected systems and versions
- Product: Oracle REST Data Services, component General
- Affected supported versions: 24.2.0 through 26.3.0
- Protocol: HTTPS, remotely exploitable without authentication
- Deployment modes in scope: ORDS runs on Oracle WebLogic Server, Apache Tomcat or standalone, on customer premises or in Oracle Cloud Infrastructure. The advisory does not restrict the issue to any one mode.
- Older releases: Oracle lists supported versions only. An unlisted older release should not be treated as confirmed safe, and Oracle's fixing policy states that unsupported releases do not receive fixes.
- Fixed build: not named publicly. Confirm it through the MOS "Database" patch availability document. ORDS 26.3.1 (
26.3.1.303.1615) is the first public release above the affected range.
Vendor security history
Oracle's security fixing policy distinguishes quarterly Critical Patch Updates (CPUs), which are cumulative where possible, from smaller Critical Security Patch Updates (CSPUs) that deliver targeted fixes for high-priority vulnerabilities without waiting for the next CPU. Beginning in June 2026, Oracle schedules CSPUs in the months outside the quarterly CPU cycle, which is how this ORDS fix arrived in November. Oracle also maintains a Security Alert program for urgent threats and recommends staying on supported releases and applying fixes without delay.
A useful reference point is CVE-2025-61882 in Oracle E Business Suite, a separate product and CVE. Oracle's Security Alert, first released October 4, 2025, described unauthenticated remote exploitation with possible remote code execution and listed the October 2023 CPU as a prerequisite. The UK National Cyber Security Centre later confirmed active exploitation. Google Threat Intelligence Group and Mandiant documented observed exploitation activity in August 2025 and, from September 29, 2025, extortion emails from an actor claiming affiliation with the CL0P brand, though Google did not formally attribute the activity to a tracked group.
The EBS case had confirmed exploitation, victim artifacts and extortion communications. The ORDS record has none of that. The EBS case also involved no user interaction, while this ORDS flaw requires it. Nothing about the EBS campaign, its actor claims or its indicators transfers to CVE-2026-114856. It does show that a published advisory and completed customer remediation are different stages.
References
- NVD: CVE-2026-114856
- CVE Record: CVE-2026-114856
- CVE Services API record for CVE-2026-114856
- Oracle Critical Security Patch Update Advisory, November 2026
- Text Form of Oracle CSPU November 2026 Risk Matrices
- Oracle ORDS and Database Actions download page
- InfraStack: CVE-2026-114856
- VulDB: CVE-2026-114856
- Introduction to Oracle REST Data Services (26.3)
- ORDS Best Practices, Oracle
- REST Data Services, Oracle
- Security Fixing Policies, Oracle
- Oracle Security Alert CVE-2025-61882
- NCSC: Active exploitation of vulnerability affecting Oracle E Business Suite
- Google Cloud Blog: Oracle E Business Suite Zero Day Exploited in Widespread Extortion Campaign
- FIRST CVSS v3.1 Specification Document
- DB Engines Ranking
- Oracle Named a Leader in the 2024 Gartner Magic Quadrant for Cloud Database Management Systems
- CISA Known Exploited Vulnerabilities Catalog
- CISA: The KEV Catalog



