CVE-2026-46842
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 unauthenticated attacker with network access via HTTPS to compromise Oracle REST Data Services. Successful attacks of this vulnerability can result in unauthorized update, insert or delete access to some of Oracle REST Data Services accessible data. CVSS 3.1 Base Score 5.3 (Integrity impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/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 confidenceVulnerability in Oracle REST Data Services (ORDS) allows unauthenticated attackers with network access via HTTPS to perform unauthorized update, insert or delete operations on accessible data. The flaw is in the Core component and affects versions 24.2.0-26.1.0. Exploitation requires no authentication or user interaction, with low integrity impact but no confidentiality or availability impact.
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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/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 checksWork through these to decide whether this CVE applies to you.
-
Identify if ORDS is installedCheck for ORDS installation by looking for the ords.war file, ORDS installation directory, or running processes containing 'ords' in the name. Common paths include $ORACLE_HOME/ords/ or /opt/ords/.Affected if ORDS software is found running or installed on the system
-
Determine installed ORDS versionRun 'java -jar ords.war version' or check the ords.war file version in the installation directory, or query the /ords/metadata-catalog endpoint if accessible.Affected if The version is >= 24.2.0 and <= 26.1.0
-
Verify ORDS is exposed on networkCheck if ORDS HTTP/HTTPS listener ports (typically 8080, 8443, or custom ports) are bound to network interfaces accessible from outside localhost. Review firewall rules and reverse proxy configurations.Affected if ORDS endpoints are reachable from network addresses beyond localhost
-
Confirm ORDS handles data operationsReview ORDS configuration files (defaults.xml, ords.conf) and check which database connections ORDS is configured to access. Identify if the connected databases contain sensitive or valuable data.Affected if ORDS is configured to connect to databases or data sources
-
Check for unauthenticated endpointsReview ORDS configuration for RESTful services or AutoREST enabled schemas that accept unauthenticated write operations. Check /ords/ endpoint accessibility without authentication.Affected if Unauthenticated write operations (INSERT, UPDATE, DELETE) are possible through ORDS endpoints
The environment is affected if ORDS versions 24.2.0 through 26.1.0 are installed and accessible over the network with any database connections configured.
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 security patch for this vulnerability when released. Until then, restrict network access to ORDS endpoints to trusted sources only and monitor for unauthorized data manipulation attempts.
- Consultation2.0 h
- Implementation4.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,096.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-46842 — 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-46842 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