dbcve.org
Rest Data ServicesApplication · Oracle

CVE-2026-46829

HIGH · 7.5 CVSS v3.1 Published 2026-05-28
Fix available
A fix is available. Upgrade to after 26.1.0 or later.
See remediation →
84/100
Remediation priority · High
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: Mongoapi). 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 hang or frequently repeatable crash (complete DOS) of Oracle REST Data Services. CVSS 3.1 Base Score 7.5 (Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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 · high confidence

Denial of service vulnerability in Oracle REST Data Services Mongoapi component. Unauthenticated remote attackers can exploit this via HTTPS to cause the service to hang or crash completely.

MitigationApply Oracle's latest security patch for Oracle REST Data Services (upgrade beyond version 26.1.0) or apply the relevant patch if available from Oracle.

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
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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. Confirm ORDS installation and version
    Locate the ORDS installation directory and check the version. Common locations include $ORACLE_HOME/ords/, /u01/oracle/ords/, or C:\oraclexe\app\oracle\product\ords\. Check for a version file or run 'java -jar ords.war version' from the ORDS home directory.
    Affected if The installed ORDS version falls within 24.2.0 through 26.1.0 inclusive.
  2. Identify if Mongoapi module is configured
    Examine the ORDS configuration directory for the mongoapi module configuration. Look for files named mongoapi*.xml, properties files containing 'mongoapi', or entries in the ords_conf.xml that reference 'mongoapi' or 'mongo'. Check the /etc/ords/ directory or the configured ORDS config path.
    Affected if The Mongoapi module is explicitly enabled or configured in the ORDS environment.
  3. Check for HTTPS endpoint exposure
    Review theORDS standalone server configuration (ords.xml, standalone.properties) or the application server deployment descriptor. Identify whether HTTPS listeners are enabled and note the bind addresses and ports. Common ports are 8443, 443, or configured custom ports.
    Affected if ORDS is accessible over HTTPS on an exposed network interface, allowing remote attackers to reach the Mongoapi endpoints.
  4. Verify service accessibility without authentication
    Confirm that the ORDS Mongoapi endpoints do not require authentication. Check the ORDS security configuration, any middleware policies, or test access to the /ords/mongoapi/ endpoint path without providing credentials.
    Affected if The Mongoapi endpoint is reachable over HTTPS without requiring authentication, which is the default vulnerable configuration.

A user is affected if ORDS version 24.2.0 through 26.1.0 is installed with the Mongoapi component enabled and exposed over HTTPS without authentication controls.

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 latest security patch for Oracle REST Data Services (upgrade beyond version 26.1.0) or apply the relevant patch if available from Oracle.

Recommended fix High confidence

Oracle REST Data Services version 26.2.0 or later (or the latest available release)

  1. 1. Identify the current Oracle REST Data Services version by checking the ORDS configuration or running 'java -jar ords.war version'
  2. 2. Download the latest Oracle REST Data Services release from Oracle Support (support.oracle.com) or Oracle Technology Network
  3. 3. Back up the current ORDS configuration, wallet files, and database connection settings
  4. 4. Deploy the new ORDS WAR file to the application server (WebLogic, Tomcat, or standalone mode)
  5. 5. Verify the ORDS application starts successfully and responds to requests
  6. 6. Test that the Mongoapi endpoint functionality works as expected
  7. 7. Monitor logs for any errors or resource consumption issues
Caveat Review Oracle's release notes for any deprecated features or configuration changes between 26.x versions

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
  • Testing8.0 h
  • Review / QA4.0 h
24.0 hours of engineering $4,160
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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