Automated Threat Modeling

Quick Look: CVE-2026-46833 — Oracle Database Net Service TLS Takeover with Scope Change

A brief summary of CVE-2026-46833, a CVSS 9.0 vulnerability in Oracle Database Net Service that lets unauthenticated attackers achieve full takeover via TLS, with impact that extends beyond the vulnerable component to additional products.

CVE Analysis

9 min read

ZeroPath CVE Analysis
ZeroPath CVE Analysis

2026-05-28

Quick Look: CVE-2026-46833 — Oracle Database Net Service TLS Takeover with Scope Change
Experimental AI-Generated Content

This CVE analysis is an experimental publication that is completely AI-generated. The content may contain errors or inaccuracies and is subject to change as more information becomes available. We are continuously refining our process.

If you have feedback, questions, or notice any errors, please reach out to us.

[email protected]

Introduction

Every client connection to Oracle Database passes through its networking layer before it reaches the database engine. CVE-2026-46833 is a critical vulnerability in that layer. It lets an unauthenticated attacker achieve full takeover via TLS and then pivot to affect products beyond the vulnerable component itself. Oracle disclosed it on May 28, 2026, in its first monthly Critical Security Patch Update. It carries a CVSS 3.1 score of 9.0 and affects client-only installations as well as database servers, so the remediation work extends well beyond the database tier into application servers, web servers, and developer workstations.

Technical Information

The Vulnerable Component: Oracle Net Services

Oracle Net Services is the networking foundation of Oracle Database. It handles every part of client-to-server and server-to-server connectivity: session establishment, authentication negotiation, encryption via TLS/SSL, and data transport. Every Oracle Database deployment relies on Net Services, and the Oracle listener (typically on TCP port 1521) is the entry point for all incoming connections. A flaw at this layer matters more than most because it sits in the path of every database interaction.

CVSS Vector Decomposition

The full CVSS 3.1 vector for CVE-2026-46833 is CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H. The metrics break down as follows:

CVSS MetricValueSignificance
Attack Vector (AV)NetworkExploitable remotely over the network
Attack Complexity (AC)HighRequires specialized conditions or knowledge
Privileges Required (PR)NoneNo authentication credentials needed
User Interaction (UI)NoneNo user action required
Scope (S)ChangedImpact extends beyond the vulnerable component
Confidentiality (C)HighComplete information disclosure possible
Integrity (I)HighComplete data modification possible
Availability (A)HighComplete service disruption possible

A High Attack Complexity rating raises the bar for exploitation compared with easily exploitable flaws, but it does not remove the threat from determined or well-resourced actors. HexRabbit of DEVCORE, a firm that specializes in enterprise network software vulnerabilities, discovered the flaw. A professional-grade discovery like this suggests the conditions for exploitation are more achievable in practice than the raw CVSS metric implies, particularly for sophisticated threat actors.

The Scope Change Problem

The Scope: Changed designation is the most operationally significant part of this CVE. In CVSS 3.1, a scope change means the vulnerability's impact crosses trust boundaries, so an attacker can affect resources outside the security authority of the vulnerable component. Oracle's advisory states that successful attacks may "significantly impact additional products." In concrete terms, compromising Net Service could cascade to the database server process itself, to connected applications, or to other systems that interact with the database over TLS. That makes CVE-2026-46833 a potential pivot point for broader infrastructure compromise, with reach well past the database.

TLS as the Attack Surface

The attack runs over TLS. Because the vulnerability requires no authentication and no user interaction, an attacker needs only network reachability to an Oracle Database listener with TLS enabled. The attack surface therefore includes any network path that can reach the listener port. Oracle has not publicly disclosed the specific exploitation mechanism, whether it involves a flaw in the TLS handshake, session management, certificate validation, or another part of the TLS implementation. That silence is consistent with Oracle's policy of withholding detailed exploit information.

Systemic Weakness: Three Net Service TLS Vulnerabilities

Oracle patched two more Net Service vulnerabilities, CVE-2026-46834 and CVE-2026-46835, in the same May 2026 CSPU. All three are remotely exploitable without authentication, and all three target TLS communications. The Oracle Database Server product family received exactly 3 new security patches in this CSPU, and every one of them addresses the same component and protocol. Three distinct vulnerabilities in the same TLS implementation, disclosed together, strongly suggest a systemic issue that warranted focused remediation rather than three unrelated bugs.

Client-Side Exposure

The Oracle advisory confirms that this vulnerability also affects client-only installations, a detail organizations may overlook. Systems running Oracle Instant Client or the full Oracle Client (without a database server) are vulnerable. These are commonly deployed on application servers, web servers, middleware tiers, and developer workstations. The remediation scope is therefore significantly larger than "patch the database servers."

Affected Systems and Versions

The following are affected:

  • Oracle Database Server versions 23.4.0 through 23.26.2
  • Client-only installations of Oracle Database (Oracle Instant Client, full Oracle Client) for the same version range
  • Any deployment where TLS is enabled for Oracle Net Services connectivity

The vulnerability is reachable through the Oracle Database listener, typically on TCP port 1521, when TLS is configured.

Vendor Security History

Oracle's security record gives useful context for CVE-2026-46833.

The April 2026 Critical Patch Update addressed 481 security vulnerabilities across Oracle's product portfolio, and approximately 78% of those patches addressed non-Oracle CVEs in bundled open-source components. Oracle Database Server itself received 8 new security updates in that release, with a maximum CVSS of 7.5. Multiple product families had vulnerabilities scoring 9.0 or higher.

Oracle's recent breaches show the consequences of delayed patching. In November 2025, attackers exploited Oracle's E-Business Suite via outdated servers and exfiltrated data from nearly 30 major corporations. A separate 2025 breach of Oracle Health's legacy Cerner systems compromised patient data across at least 16 health systems, and notifications did not go out until early 2026. FINRA issued a cybersecurity alert about an alleged large-scale data breach possibly affecting Oracle Cloud services at member firms and third-party providers.

Oracle acknowledges the pattern. It says it "continues to periodically receive reports of attempts to maliciously exploit vulnerabilities for which Oracle has already released security patches," and that attackers often succeed "because targeted customers had failed to apply available Oracle patches."

The move to monthly CSPUs, beginning with the May 28, 2026 release that includes the fix for CVE-2026-46833, is Oracle's response to this accelerating threat environment. Oracle's Integrated Cyber Center stated that "CSPUs provide targeted fixes for critical vulnerabilities in a smaller, more focused format, allowing customers to address high priority issues without waiting for the next quarterly release."

References

Detect & fix
what others miss

Works with
  • GitHub
  • GitLab
  • Bitbucket
  • Azure DevOps Services
  • Gerrit
  • CVS
  • Jira
  • Linear
  • Slack
  • Security Compass
Explore integrations
Security magnifying glass visualization