dbcve.org
Database ServerDatabase / datastore · Oracle

CVE-2026-46833

CRITICAL · 9.0 CVSS v3.1 Published 2026-05-28
Fix available
A fix is available. Upgrade to after 23.26.2 or later.
See remediation →
99/100
Remediation priority · Urgent
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 the Net Service component of Oracle Database Server. Supported versions that are affected are 23.4.0-23.26.2. Difficult to exploit vulnerability allows unauthenticated attacker with network access via TLS to compromise Net Service. While the vulnerability is in Net Service, attacks may significantly impact additional products (scope change). Successful attacks of this vulnerability can result in takeover of Net Service. CVSS 3.1 Base Score 9.0 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:H/PR:N/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 confidence

Oracle Database Server Net Service contains a critical vulnerability (CVSS 9.0) in versions 23.4.0-23.26.2 that allows unauthenticated attackers with network access via TLS to compromise the Net Service component. The vulnerability has a scope change, meaning successful exploitation may impact additional products beyond Net Service, potentially leading to complete takeover of the Net Service component.

MitigationApply Oracle Critical Patch Updates (CPU) for the affected Oracle Database versions. If immediate patching is not possible, restrict network access to Oracle Net Service listeners (typically port 1521) to trusted sources only, as the attack requires network access via TLS.

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
Database ServerDatabase / datastore
Affected:>= 23.4.0, <= 23.26.2

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

CVSS:3.1/AV:N/AC:H/PR:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify Oracle Database Server installation and version
    Use Oracle utilities such as SQL*Plus with 'SELECT VERSION FROM V$INSTANCE;' or run 'opatch lsinventory' to obtain the installed Oracle Database Server version. Alternatively, check via Oracle Enterprise Manager or Oracle Inventory.
    Affected if The installed version falls within 23.4.0 through 23.26.2 inclusive.
  2. Confirm Net Service component is present
    Check for the presence of Oracle Net Services (Oracle Net Listener) using 'lsnrctl status' or by verifying the Oracle Home directory contains netwrok/admin configuration files. Net Service is typically installed with Oracle Database Server installations.
    Affected if The Net Service (Oracle Net Listener) component is installed and configured on the system.
  3. Verify TLS listener exposure
    Run 'lsnrctl status' and review listener.ora configuration to determine if the listener is configured for TLS connections. Check for TCPS protocol in the listener configuration or active TLS-bound ports.
    Affected if The Oracle Net Listener is configured to accept connections over TLS (TCPS) and is network-accessible.
  4. Check network accessibility of the listener
    Use netstat, ss, or nmap to verify that the Oracle Net Listener port (default 1521 or custom port) is listening on accessible network interfaces and is reachable from external network segments.
    Affected if The listener port is exposed to untrusted networks rather than isolated locally or to trusted segments only.

If Oracle Database Server version 23.4.0 through 23.26.2 is installed with Net Service enabled and the TLS listener is network-accessible, the environment is vulnerable to unauthenticated remote compromise.

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.

From vendor data
Upgrade available Upgrade to a release after 23.26.2
Interim mitigation

Apply Oracle Critical Patch Updates (CPU) for the affected Oracle Database versions. If immediate patching is not possible, restrict network access to Oracle Net Service listeners (typically port 1521) to trusted sources only, as the attack requires network access via TLS.

Fix this in Database Server Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
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,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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