On this page (7 sections)

A critical vulnerability, tracked as CVE-2026-114856, has been published for Oracle REST Data Services (ORDS). The record describes an issue in the "General" component that an unauthenticated attacker with network access over HTTPS could use to take over the product. It carries a CVSS 3.1 base score of 9.6.

If you run ORDS to expose Oracle databases as REST APIs, or you host it for clients, this is worth checking today. The public record is short, so this article separates what is confirmed from what is still unknown.

What happened

The vulnerability was published by the National Vulnerability Database on November 17, 2026 and added to the GitHub Advisory Database the next day. The description points to an Oracle security alert as the reference for the vendor's details. The NVD entry repeats the same text as the GitHub advisory, so these are not two independent confirmations.

Only one independent publisher covers the story so far. The GitHub advisory is marked "Unreviewed" and lists no package, no patched versions and no weakness type (CWE). Treat the details below as the vendor's own summary, not as independently verified research.

Technical details

According to the record, the flaw is easily exploitable by an unauthenticated attacker who can reach ORDS over HTTPS. A successful attack "can result in takeover of Oracle REST Data Services". The CVSS vector is CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H, which breaks down as follows.

CVSS 3.1 metrics for CVE-2026-114856
MetricValueWhat it means in practice
Attack vectorNetworkCan be attempted remotely over HTTPS
Attack complexityLowNo special conditions needed
Privileges requiredNoneNo login needed
User interactionRequiredA person other than the attacker must take part
ScopeChangedImpact can reach other products beyond ORDS
Confidentiality / Integrity / AvailabilityHigh / High / HighFull impact on all three

The user-interaction requirement is the key detail. It means an attacker would need another person, such as an administrator or user, to do something as part of the attack. The sources do not say what that action is, and they do not name the underlying weakness class. The changed scope means the impact may extend beyond ORDS itself to other products.

The sources do not describe the root cause, the affected endpoint or any proof of concept. Do not rely on third-party claims about how the flaw works until Oracle's alert or a reputable researcher confirms them.

Who is affected

Affected are Oracle REST Data Services supported versions from 24.2.0 to 26.3.0. Realistic exposure is highest for:

  • Organizations that publish ORDS directly to the internet to serve REST APIs or web tools.
  • Hosting providers and agencies running ORDS on behalf of customers.
  • Teams where ORDS sits in front of a production Oracle database, since a scope change raises the potential blast radius.
  • Environments where ORDS is bundled with another Oracle product and the version is not tracked separately.

Instances reachable only from a restricted internal network have a smaller attack surface, but the user-interaction requirement means internal staff could still be the trigger, so do not skip them.

How to check your exposure

Start by finding every ORDS instance and working out which version it runs. The research does not give a version-check command, so use the method in Oracle's official ORDS documentation for your installation type, and compare the result with the affected range of 24.2.0 through 26.3.0. The Oracle security alert is the place to confirm which releases are covered.

  • List every host, container or application server that runs ORDS, including instances managed by vendors or hosting providers.
  • Record the installed version of each using Oracle's documented method.
  • Check whether each instance's HTTPS listener is reachable from the internet by reviewing firewall rules, load balancer and reverse proxy configuration.
  • Note which databases and other products each instance connects to, because the scope change means impact may reach them.

What to do now

The sources do not name a fixed version, so the vendor alert is the authority for the exact patch. Plan the work around it.

  1. Inventory every Oracle REST Data Services instance, including ones bundled with other products and ones run by vendors or hosting providers.
  2. Record each version and flag anything from 24.2.0 through 26.3.0.
  3. Open the Oracle security alert and identify the patched release or patch for your version.
  4. Apply the update in a test environment first, then to production, starting with internet-facing instances.
  5. Until you can patch, restrict network access to ORDS to the clients that need it, using firewall rules or a VPN.
  6. Warn administrators and users who work with ORDS to be cautious about unexpected links or requests, since the attack needs another person's involvement.
  7. After patching, review ORDS and database access logs for unusual activity from before the update.
Caution. Updating ORDS usually means restarting the service or redeploying the application, which interrupts the REST APIs that depend on it. Schedule a maintenance window and back up your ORDS configuration first.

For a broader hardening baseline on externally exposed services, see our guide to small business website security and what a WAF is. A web application firewall can add a filtering layer, but it is not a substitute for installing the vendor patch.

Detection and monitoring

No indicators of compromise have been published in the sources, so detection has to be general. Review the access logs of any web server or proxy in front of ORDS for unfamiliar client addresses, unusual request volumes or unexpected endpoints.

  • Watch for new or modified ORDS configuration, new database users and unexpected REST endpoints.
  • Alert on unusual outbound connections from the ORDS host.
  • Track changes to the HTTPS certificate and DNS records for your ORDS hostnames; Webforta Monitor offers certificate and DNS change monitoring, which helps spot tampering around exposed services.
  • Re-check Oracle's alert and the NVD record for updates, since the entry is new and may be revised.

If you run several Oracle products, review their advisories together rather than one at a time. Our security news and analysis section collects related write-ups.

What is still unknown

  • The fixed version or patch identifier is not stated in the sources reviewed.
  • There is no confirmation of exploitation in the wild in the sources, and the research data contains no CISA KEV entry for this CVE. That leaves exploitation unconfirmed, not ruled out.
  • The weakness type and the exact user action needed for an attack are not described.
  • The GitHub advisory is unreviewed and lists no package or affected-version metadata, so automated dependency tools may not flag it.

Sources

This article is based on the public sources below. Details can change as vendors and researchers publish more; check the original advisories before acting on version numbers.

  1. CVE-2026-114856 - GitHub Advisory Databasegithub.com
  2. CVE-2026-114856: Vulnerability in Oracle REST Data Services (component: General).nvd.nist.gov ·
  • Oracle
  • ORDS
  • CVE-2026-114856
  • critical vulnerability
  • patching