dbcve.org
Database ServerDatabase / datastore · Oracle

CVE-2026-46835

HIGH · 7.5 CVSS v3.1 Published 2026-05-28
Fix available
A fix is available. Upgrade to after 23.26.2 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 the Net Service component of Oracle Database Server. Supported versions that are affected are 23.4.0-23.26.2. Easily exploitable vulnerability allows unauthenticated attacker with network access via TLS to compromise Net Service. Successful attacks of this vulnerability can result in unauthorized ability to cause a hang or frequently repeatable crash (complete DOS) of Net Service. 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 Database Server's Net Service component affecting versions 23.4.0-23.26.2. Easily exploitable via unauthenticated network access through TLS, allowing attackers to cause Net Service to hang or repeatedly crash.

MitigationApply Oracle critical patch updates for the affected database versions. As an interim measure, restrict network access to Net Service via TLS to trusted sources only.

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
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. Identify Oracle Database version
    Query the database using SQL: SELECT VERSION FROM V$INSTANCE; or check the Oracle inventory files in $ORACLE_HOME/inventory/ContentsXML/oraclehome.xml
    Affected if Version falls within 23.4.0 through 23.26.2 inclusive
  2. Confirm Net Service component is installed
    Check if Oracle Net Services (sqlnet.ora, listener.ora, tnsnames.ora) files exist in $ORACLE_HOME/network/admin/
    Affected if Net Service configuration files exist and the listener is configured
  3. Verify TLS listener is enabled for Net Service
    Check listener.ora for TLS or SSL configuration entries, or run lsnrctl status to examine listener configuration
    Affected if Listener is configured with TLS/SSL transport protocol and accepts network connections
  4. Check if Net Service listener is exposed to network
    Run lsnrctl status and examine the listening endpoints; verify the listener IP binding (HOST parameter in listener.ora)
    Affected if Listener is bound to a network-accessible IP address (0.0.0.0 or external IP) rather than localhost only

User is affected if running Oracle Database 23c versions 23.4.0-23.26.2 with Oracle Net Service listener configured and accessible over TLS on the network.

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 23.26.2
Interim mitigation

Apply Oracle critical patch updates for the affected database versions. As an interim measure, restrict network access to Net Service via TLS to trusted sources only.

Recommended fix Moderate confidence

Oracle Database 23c (23.4.0 or later, preferably latest 23c release)

  1. 1. Identify the current Oracle Database Server version by running: SELECT VERSION FROM V$INSTANCE;
  2. 2. Download and install Oracle Database 23c version 23.4.0 or higher (preferably the latest available 23c release) from Oracle Technology Network
  3. 3. Apply the latest Oracle Critical Patch Update (CPU) after installation to ensure all security fixes are included
  4. 4. Verify the fix by confirming the new version is beyond 23.26.2
  5. 5. Test the Net Service functionality to ensure normal operation after upgrade
Caveat Oracle Database 23c introduces new features and may have compatibility considerations; review Oracle's upgrade documentation for existing applications and configurations

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

Fix this in Database Server Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing12.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,760
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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