CVE-2026-46775
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 · uneditedVulnerability 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. 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 9.9 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:L/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 · high confidenceA critical vulnerability in Oracle REST Data Services (ORDS) Core component allows low-privileged attackers with network access via HTTPS to achieve complete takeover of the ORDS instance. The vulnerability affects versions 24.2.0 through 26.1.0 and has a scope change allowing attacks to potentially impact additional products.
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>= 24.2.0, <= 26.1.0CVSS 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
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed ORDS versionLocate the ORDS installation directory and check the version manifest or about page accessible via the ORDS endpoint. Common methods include reviewing the WAR file version, checking the ords.war file properties, or querying the /ords/_/about endpoint if accessible.Affected if The installed version falls within 24.2.0 through 26.1.0 inclusive.
-
Confirm ORDS service is runningVerify the Oracle REST Data Services process is active. This may involve checking running Java processes, service status commands specific to the deployment method (standalone, Tomcat, Docker, etc.), or attempting to reach known ORDS endpoint paths.Affected if ORDS is running and accessible, which makes the vulnerability potentially exploitable.
-
Assess network exposure of ORDS endpointsReview firewall rules, load balancer configurations, or network ACLs that control access to ORDS HTTPS endpoints. Determine if the service is listening on external interfaces or exposed to untrusted networks.Affected if ORDS HTTPS endpoints are reachable from untrusted or public networks without proper access restrictions.
-
Check for unauthorized configuration modificationsInspect ORDS configuration files (such as defaults.xml, ords/conf standalone properties) for unexpected changes, new admin accounts, or modifications to security-related settings that could indicate exploitation attempts.Affected if Unexpected changes exist in ORDS configuration files, particularly those affecting authentication, authorization, or administrative settings.
A user is affected if their ORDS installation version is 24.2.0 through 26.1.0 and the service is running and network-accessible, regardless of whether indicators of compromise are present.
Generated from the published advisory. Verify against your own configuration.
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 dataApply Oracle's latest security patch for ORDS to upgrade beyond version 26.1.0, or follow Oracle's specific remediation guidance in the corresponding Critical Patch Update.
- Consultation2.0 h
- Implementation4.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,864.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-46775 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-46775 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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