Automated Threat Modeling

Brief Summary: CVE-2026-114848, a Critical Oracle Text Component Takeover in Oracle Database Server (CVSS 9.9)

A brief summary of CVE-2026-114848, a CVSS 9.9 flaw in the Oracle Text component of Oracle Database Server that lets a low-privileged user with Create Session take over Oracle Text over Oracle Net. It covers the disclosed attack conditions, affected versions, and patch information from Oracle's November 2026 Critical Security Patch Update.

CVE Analysis

7 min read

Gaurav Sarraf
Gaurav Sarraf

2026-11-17

Brief Summary: CVE-2026-114848, a Critical Oracle Text Component Takeover in Oracle Database Server (CVSS 9.9)

Introduction

According to Oracle, any database account holding nothing more than the Create Session privilege could take over the Oracle Text component of Oracle Database Server over Oracle Net. Oracle rates the issue at CVSS 3.1 9.9 with a changed scope, so the assessed impact is not confined to text search. The fix shipped in the November 2026 Critical Security Patch Update on November 17, 2026.

This post is a brief summary of what Oracle and the public records disclose about CVE-2026-114848, what they leave out, and how to confirm you are patched. As of publication, the sources we reviewed do not establish active exploitation, a public exploit, or a named threat actor for this CVE.

Technical information

The affected component

Oracle Text provides indexing, word and theme searching, and viewing capabilities for text query and document classification applications. Oracle lists document collection, catalog information, document classification, and XML search among its application categories. These describe what the component does. They are not a disclosed exploit delivery mechanism.

Because Oracle Text runs inside the database server, the vulnerable code lives on hosts running Oracle Database Server, not on client-only installations.

Root cause: what is and is not disclosed

Oracle does not publish root cause or code-level details for its security patch fixes, and this one is no exception. The public description establishes prerequisites and consequences, but it does not identify the vulnerable function, package, request format, payload, or exploitation sequence. No CWE is populated in the NVD record.

That means we cannot responsibly label this as SQL injection, a buffer overflow, a deserialization flaw, or any other specific class. Oracle has not said whether its fix tightens input handling, privilege checks, or memory safety, so treat any third-party claim about the specific code change with skepticism unless Oracle confirms it.

Two further boundaries apply:

  • "Takeover of Oracle Text" does not, on the available evidence, establish operating system root or SYSTEM access.
  • The scope change warning names no specific additional affected products. Under the FIRST CVSS v3.1 specification, Scope concerns impacts beyond the vulnerable component's security scope. It does not identify a particular downstream victim.

The 9.9 Critical score is Oracle's CNA assessment as displayed by NVD. NVD's own assessment was not yet provided at publication. Both NVD and the CVE record show publication on November 17, 2026.

Attack conditions

Oracle's advisory risk matrix records:

  • Component: Oracle Text
  • Privilege required: Create Session
  • Protocol: Oracle Net
  • Remotely exploitable without authentication: No
  • CVSS 3.1: 9.9

The published vector is:

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H

Broken down:

  • Attack Vector, Network: network access is part of the attack path, specifically via Oracle Net.
  • Attack Complexity, Low: Oracle describes the flaw as easily exploitable.
  • Privileges Required, Low: the attacker needs only the Create Session privilege, not administrative rights.
  • User Interaction, None: no other user has to participate.
  • Scope, Changed: impacts may extend beyond Oracle Text's security scope.
  • Confidentiality, Integrity, Availability: High.

This is a critical vulnerability that requires authentication. In practice, though, Create Session is the baseline privilege for connecting to the database at all, so any account that can log in meets the stated privilege requirement.

Attack flow, as far as it is disclosed

Based solely on Oracle's description and vector, the attack path looks like this:

  1. The attacker holds, or obtains, a database account with the Create Session privilege.
  2. The attacker reaches the database over the network using Oracle Net.
  3. Over that session, the attacker triggers the undisclosed flaw in Oracle Text. No interaction from another user is required, and Oracle rates the complexity as low.
  4. A successful attack results in takeover of Oracle Text, with high confidentiality, integrity, and availability impact and a scope change indicating possible effects beyond the component.

Step 3 is intentionally vague because the public record is. We are not aware of a verified public exploit, and we have not reproduced one.

Threat context

Oracle's "easily exploitable" wording speaks to exploitability, not to observed intrusions. VulDB lists the CISA KEV status for this CVE as "no", but that is a third-party status indication. CISA describes its catalog as a list of vulnerabilities known to have been exploited, and absence from it is not proof that exploitation has never occurred. Severity and confirmed threat activity are separate questions here, and only the first has a clear answer.

Patch information

Oracle fixed CVE-2026-114848 in its November 2026 Critical Security Patch Update (CSPU), released on November 17, 2026 (advisory Rev 1, "Initial Release"). Oracle Database is closed source, so there is no public commit or diff. The fix ships as binary Oracle Database patches available from My Oracle Support to customers with a valid support contract. You can confirm the fix from the advisory and risk matrix, but you cannot inspect the code.

Where it sits in the advisory

The CVE appears in the Oracle Database Server risk matrix of the November 2026 advisory. It is one of 7 new security patches for Oracle Database products in this CSPU, and Oracle states that none of these Database patches apply to client-only installations. The fix belongs on hosts running Oracle Database Server.

Before the patch, any user who could log in with Create Session over Oracle Net could take over Oracle Text, with the changed scope implying possible spillover into the wider database. The patch removes that path inside the Oracle Text code. Beyond that, the mechanism is not public.

Getting the right patch

  • The advisory points to My Oracle Support Doc ID CPU431 for Database patch availability. That document maps each supported release line to its patch.
  • Oracle's announcement blog post also references an executive summary for the November 2026 CSPU on My Oracle Support, Doc ID CPU433.
  • The affected ranges end at 19.33, 21.24, and 23.26.3. Systems at or below those levels need the November 2026 CSPU content for their release line. Oracle's public pages do not name the exact fixed Release Update numbers, so use Doc ID CPU431 to get the exact patch ID rather than assuming the next version number is fixed.
  • Oracle patches are usually cumulative. Applying the November 2026 CSPU, or any later patch for your release line, should include this fix along with earlier security fixes. "Usually" is Oracle's word, so check the patch documentation rather than treating it as an unconditional rule.

Verifying installation

With no public code to check, verification is a patch inventory exercise. After installing, use the standard Oracle tooling, opatch lspatches and datapatch, or query DBA_REGISTRY_SQLPATCH, to confirm that the November 2026 CSPU patch is installed in the Oracle home and registered in every database running on that home, including all PDBs in a CDB. A patched binary home with an unregistered PDB is an easy gap to miss.

Interim risk reduction

The November advisory includes general guidance, not a CVE-specific workaround, for organizations that cannot patch immediately:

  • Blocking network protocols required by an attack may reduce the risk of a successful attack, but may break application functionality.
  • Removing unnecessary privileges or package access may reduce risk where exploitation requires that access, but may also break functionality.
  • Changes should be tested on nonproduction systems first.

Oracle explicitly states that neither protocol blocking nor privilege removal is a permanent solution, because neither corrects the underlying problem. For this CVE, Oracle Net and Create Session are the disclosed prerequisites, which makes this guidance relevant. The sources supply no specific firewall rule, revocation command, or assurance that a given configuration change fully prevents exploitation.

Affected systems and versions

Oracle Database Server with the Oracle Text component, in these supported version ranges (upper bounds inclusive):

  • Oracle Database 19: 19.3 through 19.33
  • Oracle Database 21: 21.3 through 21.24
  • Oracle Database 23: 23.4.0 through 23.26.3

Configuration notes from the disclosure:

  • Exploitation requires network reachability via Oracle Net and an account with the Create Session privilege.
  • Client-only installations are not covered by the Database patches in this CSPU, per Oracle.
  • NVD and the CVE record define these inclusive ranges but do not establish a universal fixed build immediately above each boundary.
  • Oracle provides patches only for versions under Premier Support or Extended Support. Releases outside those phases are not tested for the vulnerabilities in this update, and Oracle recommends upgrading them. Absence from the listed ranges should not be read as proof that an unsupported release is safe.

Vendor security history

Oracle runs a structured, recurring patch program. Critical Patch Updates deliver security fixes for supported products, Critical Security Patch Updates complement the quarterly cumulative update program, and Security Alerts cover fixes judged too critical to wait for the next scheduled release. DB Engines ranks Oracle first in its November 2026 database popularity ranking. That is a popularity measure, not an installation count or a measure of exposed Oracle Text systems.

The most relevant recent precedent is CVE-2025-61882 in Oracle EBS, a different product and component. Google Threat Intelligence Group and Mandiant reported an extortion campaign by actors claiming affiliation with the CL0P brand, with significant data exfiltration in some cases. GTIG stated it had not formally attributed the activity to a tracked threat group and that use of the CL0P brand alone did not establish FIN11 attribution. Oracle released emergency patches on October 4, 2025, and CISA added the CVE to its KEV catalog on October 6, 2025, marking it as known to be used in ransomware campaigns.

That case shows the operational cost when an Oracle vulnerability is exploited, but it offers no basis to transfer its attack mechanism, indicators, or actors to CVE-2026-114848. Oracle's November advisory also notes, as a general warning, that it continues to receive reports of attempted exploitation of already patched vulnerabilities, and that some attacks succeed because customers have not applied available patches.

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