Skip to main content

Oracle ORDS EUVDEUVD-2026-105790

| CVE-2026-101374 MEDIUM
Improper Access Control (CWE-284)
2026-10-20 secalert_us@oracle.com GHSA-966c-8wf3-gcxr
5.9
CVSS 3.1 · Vendor: oracle
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Reach exposed ORDS HTTP endpoint
  2. Exploit
    Craft malicious request satisfying complex precondition
  3. Execution
    Bypass integrity controls on backend
  4. Impact
    Create/modify/delete critical data

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V8 - Authorization Access control enforcement
MITRE ATT&CK

1 technique across 1 tactic: Defense Evasion

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

Exploitation targets the Oracle REST Data Services Backend-as-a-Service component over HTTP and requires no authentication (PR:N) and no user interaction (UI:N), but is explicitly rated 'difficult to exploit' (AC:H) - meaning success depends on specific conditions outside the attacker's control, such as particular request timing, backend data state, or environmental factors that Oracle has not detailed. The primary limiting factors are the High attack complexity and the fact that only ORDS versions 24.2.0 through 26.1.0 are affected; the attack also requires an ORDS instance to be network-reachable on its HTTP interface, so instances not exposed beyond trusted networks face substantially reduced risk. Impact is confined to data integrity (create/delete/modify), with no data disclosure or service disruption.

Impact

This is a moderate-risk, not top-priority, vulnerability despite affecting an internet-facing component. The CVSS 3.1 vector (AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N, base 5.9) shows a conflicting risk profile: it is network-reachable and requires no authentication (PR:N) or user interaction (UI:N), which raises exposure, but attack complexity is High (AC:H), meaning successful exploitation depends on conditions outside the attacker's control (e.g., winning a race, specific data state, or non-trivial preconditions) - Oracle's own description explicitly calls it 'difficult to exploit.' Impact is narrow: integrity only (I:H), with no confidentiality (C:N) or availability (C:N/A:N) impact, so an attacker can create, delete, or modify data but cannot read it or take the service down. No EPSS score, no CISA KEV listing, and no public POC were provided in the intelligence, so there is no evidence of active exploitation or weaponization - no public exploit identified at time of analysis. The AC:H rating combined with absence of KEV/EPSS/POC signals strongly suggests this is a high-CVSS-reachability but low-real-world-likelihood issue rather than a drop-everything emergency. Note: the 'Authentication Bypass' tag is not supported by the description, which describes an integrity compromise by an already-unauthenticated attacker, not a bypass of an auth control - verify intended classification with Oracle's October 2026 CPU.

Exploit ScenarioDerived

An unauthenticated attacker with network access sends a specially crafted HTTP request to an exposed Oracle REST Data Services endpoint and, by satisfying a difficult-to-achieve precondition (AC:H), manipulates backend data to create, alter, or delete records in Oracle REST Data Services-accessible data. Because confidentiality is not impacted, the goal is tampering or sabotage rather than data theft. No public exploit code was identified, and the high attack complexity means real-world exploitation requires significant effort or favorable timing.

This Month Plan within 30 days. Why: MEDIUM severity (CVSS 4.0-6.9).
No patch listed yet 0.3% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Oct 21, 2026

Unauthenticated data tampering in Oracle REST Data Services (ORDS) versions 24.2.0 through 26.1.0 lets a remote attacker with HTTP access to an exposed instance create, delete, or modify critical application data, with no confidentiality or availability impact. Oracle rates the flaw 'difficult to exploit' (AC:H), so success depends on conditions outside the attacker's control such as request timing, backend data state, or environment specifics that the vendor has not detailed. No public exploit code or confirmed active exploitation was identified at time of analysis, and no EPSS score was supplied; exposure is limited to ORDS deployments reachable over the network on their HTTP interface, particularly 26.1.0 and earlier releases lacking the October 2026 Critical Patch Update.

RemediationAI

Apply the Oracle REST Data Services fix delivered in the October 2026 Critical Patch Update (https://www.oracle.com/security-alerts/cpuoct2026.html); the advisory lists the corrected ORDS release for each supported line, but the exact patched version number is not stated in the data available here, so confirm the target build against the CPU before upgrading, and roll the patch out to every instance in the 24.2.0-26.1.0 range, including non-production copies that share database credentials. Where immediate patching is not possible, reduce exposure by placing ORDS behind a reverse proxy or WAF that restricts the /ords/ Backend-as-a-Service paths to known client networks or requires mutual TLS, accepting the operational cost of updating allowlists and potentially breaking legitimate external integrations; alternatively, bind the ORDS listener to internal interfaces or block the HTTP port at the perimeter, which eliminates internet-facing risk but removes remote API access entirely. Because exploitation is rated difficult and requires reachability plus specific backend conditions, network segmentation is an effective interim control, but it should be treated as temporary: the underlying authorization bypass remains present until the CPU is applied, and database-side auditing on ORDS service accounts should be enabled in the meantime to detect unexpected create, delete, or modify activity.

Affected VersionsENISA

Oracle REST Data Services 24.2.0 ≤26.1.0

Affected Packages

euvd oracle_rest_data_services no fix

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

Oracle REST Data Services is a Java-based mid-tier that publishes Oracle Database objects and custom handlers as RESTful HTTP endpoints, and the affected 'Backend-as-a-Service' component is the layer that exposes database-backed services to REST clients. The flaw is a request-handling/authorization weakness reachable over plain HTTP (AV:N, PR:N, UI:N) that yields integrity-only impact (I:H with C:N/A:N), consistent with an attacker being able to drive create, update, and delete operations that should have been gated by an authorization decision rather than with memory corruption or injection of arbitrary code. No CWE identifier was assigned in the available data, and Oracle has not published the underlying code path, so the exact bypass mechanism is undocumented; the vendor's 'Authentication Bypass' tagging and the High attack complexity (AC:H) together suggest the bypass only works for particular request sequences, parameter combinations, or backend data states rather than as a reliable one-shot exploit. Because the CVSS scope is unchanged, the impact stays within the ORDS instance and the database objects it fronts, and the single most important environmental factor is whether the ORDS HTTP listener is reachable from untrusted networks.

Know when the next one hits your stack

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (oracle) PRIMARY 5.9 MEDIUM
AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N
vuln.today AI 5.9 MEDIUM

Network-reachable HTTP with no auth (AV:N/PR:N/UI:N) but vendor-stated difficulty of exploitation (AC:H); integrity-only impact (I:H, C:N/A:N) per description.

3.1 AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N
4.0 AV:N/AC:H/AT:N/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N

Primary rating from Vendor (oracle).

CVSS VectorVendor: oracle

Attack Vector
Network
Attack Complexity
High
Privileges Required
None
User Interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
None

DescriptionCVE.org

Vulnerability in Oracle REST Data Services (component: Backend-as-a-Service). Supported versions that are affected are 24.2.0-26.1.0. Difficult to exploit vulnerability allows unauthenticated attacker with network access via HTTP to compromise Oracle REST Data Services. Successful attacks of this vulnerability can result in unauthorized creation, deletion or modification access to critical data or all Oracle REST Data Services accessible data. CVSS 3.1 Base Score 5.9 (Integrity impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N).

Threat Intelligence Overview

EPSS Score
0.3%
Top 81% exploitable
Prevalence
Medium
Oracle database middleware, common in Oracle shops but not universally deployed
Data Quality
4 sources
Confidence: Medium

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity MEDIUM
CISA KEV No
Public POC No
EPSS 0.3%
Patch available No
Active threat No
Deciding rule
MEDIUM severity (CVSS 4.0-6.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Scheduled
Exploitation· derived
None
System Exposure· derived
Open
Automatable· derived
No
Human Impact· derived
Medium

Priority Score

30
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +30
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy