Introduction
According to Oracle, an authenticated database user holding nothing more than the Create Session privilege could take over an Oracle Database 23.x RDBMS over Oracle Net, with impact that may extend to additional products. Oracle rated the flaw CVSS 3.1 9.9 and fixed it in the November 2026 Critical Security Patch Update. Even the newest Release Update, 23.26.4, remains vulnerable until the CSPU patch is applied on top of it.
Technical Information
What Oracle disclosed
CVE-2026-114822 sits in the RDBMS component, the core database engine of Oracle Database Server. The official description establishes three prerequisites:
- An affected Oracle Database Server release, 23.4.0 through 23.26.4
- An attacker with a low-privileged account holding Create Session
- Network access to the database via Oracle Net
Oracle describes the vulnerability as easily exploitable and states that successful attacks can result in takeover of the RDBMS. Because the scope is changed, attacks may significantly impact additional products beyond the database itself.
The published vector is:
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
Breaking that down, using the FIRST CVSS v3.1 definitions:
- Attack Vector: Network. Reachable through Oracle Net.
- Attack Complexity: Low. Consistent with Oracle's "easily exploitable" wording.
- Privileges Required: Low. Create Session is the stated requirement. No administrative role is needed.
- User Interaction: None. No other user has to take any action.
- Scope: Changed. Impact can cross the security boundary of the vulnerable component.
- Confidentiality, Integrity, Availability: High.
The consequences are severe, but exploitation requires authentication. The advisory's risk matrix explicitly marks "Remote exploit without auth" as No. Create Session, however, is the most basic privilege a database account can hold, so the population of potential attackers includes essentially any user or application account allowed to log in.
As with all CVSS base scores, 9.9 describes intrinsic characteristics of the flaw, not a probability that it will be exploited in a given environment.
Root cause: what is and is not public
Oracle Database is closed source, and this is a vendor-only fix with no public commit or diff. The CNA record lists the weakness classification as N/A rather than a specific CWE. The reviewed records do not identify the vulnerable function, the triggering SQL or protocol request, a memory-safety error, or any exploit sequence. Our view is that the evidence does not support labeling this as SQL injection, a buffer overflow, or any other specific class, and readers should be cautious of sources that do.
The advisory's risk matrix supports two inferences:
- The bug appears specific to 23.x code. The 19c and 21c lines appear for other database CVEs in the same CSPU, but not for CVE-2026-114822. That suggests the vulnerable code was introduced in the 23ai/26ai series.
- The latest RU is still affected. The affected range ends at 23.26.4, the newest Release Update, available since October 20, 2026. By contrast, the two Oracle Text CVEs in the same matrix (CVE-2026-114819 and CVE-2026-114848) have 23.x ranges ending at 23.26.3, meaning 23.26.4 already fixed them. For CVE-2026-114822, the fix exists only in the CSPU patch or a later RU that includes it.
"Takeover of RDBMS" is also not the same as operating system compromise. Oracle's description does not claim host-level code execution, and its statement that additional products may be affected leaves the precise downstream impact undefined.
Attack flow based on the disclosure
Without a published root cause, the attack flow can only be described at the level of the disclosed prerequisites and outcome:
- The attacker obtains credentials for any database account that has the Create Session privilege on an Oracle Database Server running 23.4.0 through 23.26.4.
- The attacker connects to the database over Oracle Net from a network position that can reach the listener.
- The attacker triggers the undisclosed flaw in the RDBMS component. Oracle rates this step as low complexity with no user interaction.
- On success, the attacker achieves takeover of the RDBMS, with high impact to confidentiality, integrity, and availability, and potential impact to additional products due to the changed scope.
Exploitation status
The reviewed Oracle, CVE, and NVD records do not confirm active exploitation, name a threat actor, or provide a public exploit. The examined CISA KEV snapshot (version 2026.11.17, released 17:53:15.5664Z) predates both the CNA publication (21:31:22.241Z) and the NVD publication (22:18:10.103) on the same day, so it says nothing about the post-disclosure KEV status of this CVE. Lack of a campaign report is not evidence that exploitation cannot occur.
Patch Information
Oracle fixed CVE-2026-114822 in its November 2026 Critical Security Patch Update (CSPU), published on November 17, 2026. It is one of 7 new security patches for Oracle Database Products in this CSPU, alongside some third-party component patches. The advisory's Oracle Database Server risk matrix lists it against the RDBMS component, with Create Session as the required privilege and Oracle Net as the protocol.
23.26.4 is not a fixed version. Some aggregators, such as SecurityOnline's CVE Watchtower, list 23.26.4 as the patched version. That is incorrect: Oracle's advisory and the CVE record published through NVD both list 23.26.4 as the last affected version. Upgrading to 23.26.4 alone does not remediate the issue. You need the November 2026 CSPU database patch, or a later RU that includes it.
How the fix is delivered:
- CSPU program. Oracle introduced CSPUs in 2026 to complement the CPU program, as smaller, targeted security bundles released between the quarterly cumulative Critical Patch Updates. Oracle's fixing policy states it aims to make quarterly CPUs cumulative across previously released CPU and CSPU fixes.
- Patch Availability Document. The advisory links the Database Patch Availability Document (
CPU431) on My Oracle Support, which lists the patch numbers for each 23.x RU along with installation steps. A valid support contract is required to download them. - Support phase. CSPU patches are only shipped for releases under Premier Support or Extended Support. Releases outside those phases are not tested for the bug, and Oracle recommends upgrading them.
- Server only. The database patches are not applicable to client-only installations. Only hosts running Oracle Database Server need them.
- Skipped updates. Customers who have skipped earlier patches should review previous CPU and CSPU advisories to determine appropriate actions.
- Oracle E Business Suite. Oracle recommends applying the November 2026 CSPU to the Oracle Database and Oracle Fusion Middleware components of E Business Suite deployments, with guidance in My Oracle Support document KA923.
Oracle has not published technical details of the code change itself. The patch closes the Create Session to RDBMS takeover path inside the database engine. Oracle's advisory notes that interim measures, such as blocking network protocols or revoking privileges, reduce risk but do not fix the underlying problem. Applying the patch is the actual remediation.
Affected Systems and Versions
- Product: Oracle Database Server, RDBMS component
- Affected supported versions: 23.4.0 through 23.26.4 (the 23ai/26ai line), including the newest Release Update, 23.26.4
- Not listed for this CVE: the 19c and 21c lines, which appear in the same CSPU only for other database CVEs
- Vulnerable configuration: a database server reachable over Oracle Net where an attacker can authenticate with an account holding Create Session
- Not affected by this patch set: installations containing only Oracle Database clients without Oracle Database Server
- Fixed in: the November 2026 CSPU database patch applied to the relevant 23.x RU, or a later RU that includes it
Vendor Security History
Oracle ranks first in the November 2026 DB Engines popularity ranking, which is a monthly popularity measure rather than an installed market share figure. That position makes database server disclosures broadly relevant.
Oracle's remediation process has shifted in 2026. Quarterly CPUs remain the primary mechanism for backporting fixes to on-premises products, but Oracle now supplements them with monthly CSPUs for critical vulnerabilities, with November included in the supplemental schedule beginning June 2026. Oracle's October 2026 security announcement explicitly encourages organizations to move to a monthly security patching cycle. Teams that schedule Oracle maintenance only around quarterly CPUs would have missed this fix until the next quarterly release.
The track record also includes a significant incident. Oracle's alert for CVE-2025-61882, initially released October 4, 2025, covered a flaw in the Oracle E Business Suite Concurrent Processing BI Publisher Integration component that was remotely exploitable without authentication and could lead to remote code execution. Oracle published observed indicators, and Reuters reported on October 3, 2025 that Google linked an Oracle customer extortion campaign to cl0p. That incident involved a different product, a different CVE, and an unauthenticated attack model. It does not establish exploitation of CVE-2026-114822, and its indicators should not be reused as detections for this flaw.
References
- NVD: CVE-2026-114822
- CVE Record: CVE-2026-114822
- Oracle Critical Security Patch Update Advisory, November 2026
- Text Form of Oracle CSPU November 2026 Risk Matrices
- SecurityOnline CVE Watchtower entry for CVE-2026-114822
- CVE Services API record for CVE-2026-114822
- NVD API record for CVE-2026-114822
- Oracle Security Fixing Policies
- Oracle Security Vulnerability Remediation Practices
- Oracle Security Blog: October 2026 Critical Patch Update Released
- CISA Known Exploited Vulnerabilities feed
- FIRST CVSS v3.1 Specification Document
- DB Engines Ranking
- About Oracle: Company Information
- Oracle Security Alert for CVE-2025-61882
- Reuters: Oracle says hackers are trying to extort its customers



