dbcve.org
Rest Data ServicesApplication · Oracle

CVE-2026-46830

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: 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 read access to a subset of Oracle REST Data Services accessible data. CVSS 3.1 Base Score 5.3 (Confidentiality impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/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 · moderate confidence

Information disclosure vulnerability in Oracle REST Data Services (ORDS) Mongoapi component allowing unauthenticated network attackers to read a subset of accessible data. The vulnerability affects versions 24.2.0 through 26.1.0 with low complexity exploitation requiring only network access.

MitigationApply Oracle security patches for ORDS when available, or upgrade to a patched version beyond 26.1.0. Until patched, restrict network access to ORDS endpoints via firewall or access control lists.

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/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. Identify if Oracle REST Data Services is installed
    Look for ORDS installation directories (commonly under $ORACLE_HOME/ords or /opt/ords), running ORDS processes, or ORDS-related services on the system
    Affected if ORDS is found to be installed on the system
  2. Determine the installed ORDS version
    Run 'java -jar ords.war version' from the ORDS installation directory, or check the ords.war file version metadata
    Affected if The installed version falls within >= 24.2.0 and <= 26.1.0
  3. Verify the Mongoapi module is enabled
    Check the ORDS configuration (defaults.xml or standalone.properties) for mongoapi.enabled=true, or attempt to access the /mongonaut/mongoapi endpoint if exposed
    Affected if The Mongoapi component is enabled in the ORDS configuration
  4. Confirm network exposure via HTTPS
    Check if the ORDS HTTPS listener is accessible externally by reviewing network listener configuration (e.g., standalone.properties port settings, reverse proxy rules, or firewall rules)
    Affected if ORDS is reachable over HTTPS from untrusted network locations

The environment is affected if Oracle REST Data Services versions 24.2.0 through 26.1.0 are installed with the Mongoapi component enabled and exposed to 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.

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

Apply Oracle security patches for ORDS when available, or upgrade to a patched version beyond 26.1.0. Until patched, restrict network access to ORDS endpoints via firewall or access control lists.

Recommended fix Moderate confidence

Apply Oracle's published patch for ORDS version 26.1.0 or later (refer to Oracle Critical Patch Update for exact fixed version)

  1. 1. Check Oracle's official Critical Patch Update (CPU) advisory for the specific patch addressing CVE-2026-46830
  2. 2. Identify the exact patch number and version for your Oracle REST Data Services installation
  3. 3. Download the appropriate patch from Oracle Support
  4. 4. Apply the patch following Oracle's standard patching procedure for ORDS
  5. 5. Verify the patch was applied successfully by checking the ORDS version
  6. 6. Test that the Mongoapi component is functioning correctly post-patch
Caveat Check Oracle's patch documentation for any known issues or prerequisites before applying

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

Fix this in Rest Data Services Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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