Automated Threat Modeling

Overview of CVE-2026-114819: Critical Oracle Text Takeover Flaw in Oracle Database Server

A brief summary of CVE-2026-114819, a CVSS 9.9 flaw in the Oracle Text component of Oracle Database Server that lets a low-privileged user with Create Session privilege and Oracle Net access take over Oracle Text. Includes affected versions and Oracle's November 2026 CSPU patch details.

CVE Analysis

7 min read

Gaurav Sarraf
Gaurav Sarraf

2026-11-17

Overview of CVE-2026-114819: Critical Oracle Text Takeover Flaw in Oracle Database Server

Introduction

A database account holding little more than the CREATE SESSION privilege is enough to take over Oracle Text, the full-text search engine built into Oracle Database Server, on supported releases in the 19, 21 and 23 families. Oracle rates this flaw, tracked as CVE-2026-114819, at CVSS 3.1 9.9 with a changed scope, which means a successful attack against Oracle Text may significantly affect products beyond the component itself.

Oracle fixed the issue in its November 2026 Critical Security Patch Update (CSPU), released on November 17, 2026. The reviewed public reporting does not confirm exploitation in the wild, and Oracle has not published root cause details. This post summarizes what is known, what is not, and how the fix is delivered.

Technical information

Affected component

Oracle Text provides indexing and querying functionality inside Oracle Database, including text indexes and CONTAINS queries. The vulnerability record identifies Oracle Text as the vulnerable component but does not name a specific package, procedure or query operator.

Root cause: what is and is not public

Oracle Database is closed source, so there is no public commit, diff or source-level changelog for this fix. Oracle has not released technical details about the root cause or the code change. Specifically, the public record does not disclose:

  • a malicious SQL statement or vulnerable routine
  • a payload format
  • a memory corruption mechanism or other precise root cause

No CWE is assigned in the CVE record, and a secondary record labels the weakness field N/A. Labeling this as SQL injection, improper access control or any other specific weakness class would go beyond the available evidence, so we do not.

CVSS breakdown

The published vector is:

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
  • Attack Vector: Network (Oracle Net)
  • Attack Complexity: Low
  • Privileges Required: Low (at least CREATE SESSION)
  • User Interaction: None
  • Scope: Changed
  • Confidentiality, Integrity, Availability: High, High, High

Oracle's risk matrix marks the issue as not remotely exploitable without authentication. The 9.9 score expresses severity rather than a measured probability of exploitation.

Attack flow, based on disclosed conditions

Oracle's description supports the following high-level sequence. Step 3 is intentionally abstract because the specific operation has not been disclosed.

  1. The attacker holds a database account with the CREATE SESSION privilege. Oracle describes this as a low-privileged attacker.
  2. The attacker reaches the database over the network via Oracle Net.
  3. The attacker interacts with Oracle Text in a way Oracle has not publicly described. Oracle characterizes this step as easily exploitable, with low complexity and no user interaction required.
  4. The result is takeover of Oracle Text. Because scope is changed, attacks may significantly impact additional products. The record does not name those products, and it does not establish that every connected database, application or operating system would be compromised.

In practice, this is an authenticated network vulnerability. Exposure assessment should focus on which accounts can open sessions on affected databases and which networks can reach Oracle Net.

Exploitation status

The reviewed CVE-specific page states "No confirmed exploitation yet," and a roundup of the November 2026 update lists CVE-2026-114819 as "Not exploited," with active exploitation across the update described as "None confirmed." No threat actor, public exploit or proof of concept, indicators or detection signatures are associated with this CVE in the reviewed sources. An unconfirmed status does not prove that no attacks have occurred.

Patch information

What the fix covers

The November 2026 CSPU Database risk matrix lists CVE-2026-114819 as fixed with:

  • CVSS 3.1: 9.9, vector CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
  • Protocol: Oracle Net
  • Remotely exploitable without authentication: No. At least CREATE SESSION is required.
  • Supported versions listed as affected: 19.3 through 19.32, 21.3 through 21.24, and 23.4.0 through 23.26.3

Both the advisory and NVD list affected ranges, not fixed builds. The safe reading is that a database is exposed until the November 2026 Database security patch for its release line is installed. Do not assume the next version number up already contains the fix.

How the fix is packaged

Oracle's Database Server executive summary states this CSPU adds 7 new security patches for Database Server. CVE-2026-114819 shares the risk matrix with:

  • CVE-2026-114848, also in Oracle Text
  • CVE-2026-114822, in RDBMS
  • Several fixes for third-party libraries bundled with RDBMS and Fleet Patching and Provisioning (OpenSSL, Python, Apache HttpClient, Jackson core)

Two Oracle Text fixes in one cycle suggest the full-text subsystem received focused hardening. Administrators applying the Database patch receive both Oracle Text fixes together.

Oracle started its Critical Security Patch Update program in 2026. CSPUs are smaller, targeted security bundles shipped between the regular quarterly, cumulative Critical Patch Updates (CPUs). They add to CPUs rather than replace them, which is why this Oracle Text fix shipped without waiting for the next quarterly CPU.

Getting the patch

  • Patch binaries are not public downloads. Customers with an active support contract obtain them through My Oracle Support.
  • The advisory's Patch Availability Document column for Oracle Database points to MOS document CPU431, which maps each supported release (19c, 21c, 23ai) to its patch and provides installation steps.
  • Oracle provides CSPU patches only for versions in Premier or Extended Support. It does not test releases outside those phases for this bug and states older releases are likely also affected. Such systems must move to a supported release to receive the fix.
  • If earlier security patches were skipped, Oracle advises reviewing previous CPU and CSPU advisories as well, so older Database fixes are not left uninstalled.

Verifying the fix

Since no root cause or code change is public, the only way to confirm coverage is to check that the patch named in MOS document CPU431 for your release appears in the database home's patch inventory, for example:

opatch lspatches

Interim measures if patching is delayed

Oracle's advisory includes general guidance that applies across the whole update, not a tested workaround specific to this CVE:

  • Blocking network protocols required by an attack may reduce risk until patching, but may break application functionality.
  • Removing unnecessary privileges or access to packages from users who do not need them may reduce risk, but may also break functionality.
  • Restrictive changes should be tested on nonproduction systems first.

Oracle explicitly states these restrictions are not long-term solutions because they do not correct the underlying problem. Given the disclosed prerequisites (Oracle Net access and CREATE SESSION), this guidance is relevant, but no specific firewall rule, port restriction or revocation command has been published as a complete remedy.

Affected systems and versions

Oracle Database Server, Oracle Text component, supported versions:

  • 19: 19.3 through 19.32
  • 21: 21.3 through 21.24
  • 23: 23.4.0 through 23.26.3

Vulnerable configuration: an affected database reachable over Oracle Net by an attacker holding an account with at least the CREATE SESSION privilege.

Notes:

  • These are published affected ranges, not fixed release boundaries. The CVE record does not provide a minimum corrected build.
  • One secondary aggregation page labels 19.32, 21.24 and 23.26.3 as patched while also including them in its affected ranges. The authoritative CVE record places all three inside the affected ranges, so those labels should not be treated as evidence that those releases alone resolve the issue.
  • Releases outside Premier or Extended Support were not tested by Oracle and are likely also affected.

Vendor security history

Oracle is the CVE Numbering Authority for this record. Oracle describes Critical Patch Updates as its primary mechanism for backporting security fixes to customer premises products, on a quarterly schedule. Its policy also allows patches or workaround instructions outside that schedule for particularly critical vulnerabilities or reported active exploitation, and Oracle states that it prioritizes defects according to their associated risk. The 2026 introduction of CSPUs adds a further, more frequent delivery channel. For market context, Oracle announced on January 21, 2025 that Gartner named it a Leader in the 2024 Magic Quadrant for Cloud Database Management Systems.

A materially different, unrelated precedent is CVE-2025-61882 in Oracle E Business Suite. Oracle issued a Security Alert on October 4, 2025 for that flaw, which allowed remote code execution without authentication and carried a CVSS score of 9.8. Google Threat Intelligence Group and Mandiant reported a large-scale extortion campaign by an actor claiming affiliation with the CL0P brand, involving exploitation of what may have been CVE-2025-61882 before a patch was available, with significant data exfiltration in some cases. GTIG had not formally attributed that activity to a tracked group.

That incident shows exploitation can precede public remediation for Oracle products. It establishes nothing about exploitation, attribution or a shared technical mechanism for CVE-2026-114819.

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