dbcve.org
Rest Data ServicesApplication · Oracle

CVE-2026-46840

CRITICAL · 10.0 CVSS v3.1 Published 2026-05-28
Fix available
A fix is available. Upgrade to after 26.1.0 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Vulnerability in Oracle REST Data Services (component: Backend-as-a-Service). Supported versions that are affected are 24.2.0-26.1.0. Easily exploitable vulnerability allows unauthenticated attacker with network access via HTTPS to compromise Oracle REST Data Services. While the vulnerability is in Oracle REST Data Services, attacks may significantly impact additional products (scope change). Successful attacks of this vulnerability can result in takeover of Oracle REST Data Services. CVSS 3.1 Base Score 10.0 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H).

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

This is a critical unauthenticated remote code execution vulnerability in Oracle REST Data Services (ORDS) affecting versions 24.2.0 through 26.1.0. The vulnerability in the Backend-as-a-Service component allows an attacker with network access via HTTPS to completely compromise the ORDS instance, potentially extending impact to additional products due to scope change.

MitigationApply the Oracle security patch for CVE-2026-46840 once released, or upgrade ORDS to a patched version beyond 26.1.0. Immediately restrict network exposure of ORDS interfaces to trusted sources until the patch can be applied.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Rest Data ServicesApplication
Affected:>= 24.2.0, <= 26.1.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Determine installed ORDS version
    Access the ORDS about page via HTTPS (e.g., /ords/ or /ords/_/about) or inspect the ORDS war file version metadata. If using command line, run 'java -jar ords.war --version' if applicable.
    Affected if The version falls within 24.2.0 through 26.1.0 inclusive.
  2. Verify ORDS HTTPS endpoint is network accessible
    Confirm that ORDS is listening on HTTPS and reachable from network locations. Check your firewall, load balancer, or reverse proxy configuration that exposes ORDS ports (typically 443 or custom HTTPS port).
    Affected if ORDS HTTPS endpoints are exposed to untrusted network sources.
  3. Confirm Backend-as-a-Service component is enabled
    Check if the ORDS BaaS feature is configured and active. This is typically indicated by specific ORDS endpoints or configuration in the ORDS standalone or application server deployment.
    Affected if ORDS is deployed with the Backend-as-a-Service component enabled and accessible via HTTPS.

You are affected if ORDS version is 24.2.0 through 26.1.0, the BaaS component is enabled, and ORDS HTTPS endpoints are network-accessible to untrusted sources.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to a release after 26.1.0
Interim mitigation

Apply the Oracle security patch for CVE-2026-46840 once released, or upgrade ORDS to a patched version beyond 26.1.0. Immediately restrict network exposure of ORDS interfaces to trusted sources until the patch can be applied.

Recommended fix Moderate confidence

Upgrade to ORDS version 26.2.0 or later (latest available stable release)

  1. 1. Back up the current Oracle REST Data Services (ORDS) installation and configuration
  2. 2. Download the latest Oracle REST Data Services version from Oracle Support (Oracle.com) - ensure the version is higher than 26.1.0
  3. 3. Stop the Oracle REST Data Services instance
  4. 4. Install the new ORDS version following Oracle's installation documentation
  5. 5. Restore or reconfigure the ORDS configuration files (ords-conf.xml, ords_params.properties, etc.)
  6. 6. Start the Oracle REST Data Services instance
  7. 7. Verify the service is running correctly and test that all REST endpoints function as expected
  8. 8. Review Oracle's patch notes for the new version to confirm the vulnerability is addressed
Caveat Review Oracle's release notes for potential configuration or compatibility changes between versions 24.2.0-26.1.0 and the target version

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Rest Data Services Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing10.0 h
  • Review / QA6.0 h
34.0 hours of engineering $5,940
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $9,504.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-46840 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-46840 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data