dbcve.org
Rest Data ServicesApplication · Oracle

CVE-2026-35277

HIGH · 8.1 CVSS v3.1 Published 2026-05-28
Fix available
A fix is available. Upgrade to after 26.1.0 or later.
See remediation →
87/100
Remediation priority · High
Remotely reachable 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 low privileged attacker with network access via HTTPS 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 as well as unauthorized access to critical data or complete access to all Oracle REST Data Services accessible data. CVSS 3.1 Base Score 8.1 (Confidentiality and Integrity impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N).

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 · high confidence

Vulnerability in Oracle REST Data Services (ORDS) core component allows low-privileged attackers with network access via HTTPS to create, delete, or modify critical data, as well as access critical or complete ORDS data. The vulnerability is easily exploitable with low attack complexity and no user interaction required, achieving high confidentiality and integrity impacts.

MitigationApply Oracle's available patch for ORDS versions 24.2.0-26.1.0. Until patch deployment, restrict network access to ORDS endpoints to trusted sources and monitor for unauthorized access attempts.

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

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

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 if ORDS is installed
    Look for ORDS installation directories (common paths: $ORACLE_HOME/ords, /etc/ords, C:\ords), check for ords.war file, or look for ords processes running (java processes with ords in command line)
    Affected if ORDS software is found on the system
  2. Find the installed ORDS version
    Run 'java -jar ords.war version' or check the version file in the ORDS installation directory, or access the ORDS about page at /ords/_/About
    Affected if Version cannot be determined or is in the range 24.2.0 through 26.1.0 inclusive
  3. Confirm version is within affected range
    Compare the installed version to the affected range: versions 24.2.0, 24.3.0, 24.4.0, 24.5.0, 25.1.0, 25.2.0, 25.3.0, 26.0.0, 26.1.0 are all affected
    Affected if Installed version is greater than or equal to 24.2.0 and less than or equal to 26.1.0
  4. Check if ORDS HTTPS listener is enabled
    Review ORDS configuration files (defaults.xml, ords.conf) for standalone.server.mode=HTTPS or check for SSL/TLS configuration in the application server hosting ORDS
    Affected if ORDS is configured to accept HTTPS connections and is network-accessible

If ORDS is installed with a version between 24.2.0 and 26.1.0 inclusive and the service is exposed over HTTPS, the environment is affected by this vulnerability.

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 Oracle's available patch for ORDS versions 24.2.0-26.1.0. Until patch deployment, restrict network access to ORDS endpoints to trusted sources and monitor for unauthorized access attempts.

Recommended fix Moderate confidence

Oracle REST Data Services version later than 26.1.0 (check Oracle's official patch database for the exact fixed release)

  1. 1. Identify the current Oracle REST Data Services version in your environment using the Oracle REST Data Services about page or version check utility.
  2. 2. Navigate to Oracle Support and search for Oracle REST Data Services security patches or the specific CVE-2026-35277.
  3. 3. Obtain and apply the latest Oracle REST Data Services version or security patch that addresses this vulnerability.
  4. 4. After applying the update, restart the Oracle REST Data Services instance to ensure the patch takes effect.
  5. 5. Verify the fix by confirming the updated version and testing core functionality.
Caveat Review Oracle's release notes for the new version to check for any breaking changes or deprecated features

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

Fix this in Rest Data Services Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing12.0 h
  • Review / QA6.0 h
30.0 hours of engineering $5,120
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-35277 — 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-35277 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