Rest Data ServicesApplication · Oracle

CVE-2026-46843

MEDIUM · 5.3 CVSS v3.1 Published 2026-05-28
Fix available
A fix is available. Upgrade to after 26.1.0 or later.
See remediation →
62/100
Remediation priority · Elevated
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: Core). 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. Successful attacks of this vulnerability can result in unauthorized ability to cause a partial denial of service (partial DOS) of Oracle REST Data Services. CVSS 3.1 Base Score 5.3 (Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L).

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

Oracle REST Data Services (ORDS) versions 24.2.0 through 26.1.0 contain a vulnerability in the Core component that allows unauthenticated remote attackers to cause a partial denial of service via network requests over HTTPS. The attack requires no authentication or user interaction, and exploits the availability impact vector with low complexity.

MitigationApply the Oracle patch or upgrade to ORDS version 26.2.0 or later to resolve this vulnerability. Since this is an unauthenticated DoS, consider implementing rate limiting or web application firewall rules as a temporary mitigation while planning the upgrade.

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
Unchanged
Confidentiality
None
Integrity
None
Availability
Low

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

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. Identify Oracle REST Data Services installation
    Locate the ORDS installation directory and identify the version file or startup script that contains the version number. Common locations include the ORDS home directory, war file manifest, or the configuration directory.
    Affected if ORDS is found and running in the environment
  2. Determine installed ORDS version
    Check the version of Oracle REST Data Services by examining the war file manifest, version.txt file, or running 'java -jar ords.war version' if applicable. Compare this version against the affected range of 24.2.0 through 26.1.0.
    Affected if Installed version is 24.2.0, 24.3.0, 24.4.0, 25.0.0, 25.1.0, 26.0.0, or 26.1.0
  3. Verify HTTPS network exposure
    Determine if the ORDS instance is exposed to network access via HTTPS. Check theORDS configuration for the HTTPS listener port and whether it is bound to a publicly accessible network interface.
    Affected if ORDS is listening on a reachable HTTPS port exposed to network traffic
  4. Confirm unauthenticated access path
    Verify that the ORDS endpoints are accessible without authentication. Check if the ORDS endpoints allow unauthenticated requests over the network.
    Affected if ORDS accepts unauthenticated HTTPS requests from network clients

A user is affected if Oracle REST Data Services is running with a version between 24.2.0 and 26.1.0 inclusive and is exposed to unauthenticated HTTPS network access.

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.

From vendor data
Upgrade available Upgrade to a release after 26.1.0
Interim mitigation

Apply the Oracle patch or upgrade to ORDS version 26.2.0 or later to resolve this vulnerability. Since this is an unauthenticated DoS, consider implementing rate limiting or web application firewall rules as a temporary mitigation while planning the upgrade.

Fix this in Rest Data Services Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,380
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

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-46843 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